[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: kernel define URB_ASYNC_UNLINK missing



On Thu, 2005-09-22 at 17:31 -0400, Dave Jones wrote:
> On Thu, Sep 22, 2005 at 03:13:08PM -0400, Michael H. Warfield wrote:
>  > > Not really. rawhide is always the 'upstream snapshot of the day'.
>  > > Or close to it.
>  > 
>  > 	Oh...  I see.  So kernel-2.6.13-1.1565 is really 2.6.14rc2 (I see the
>  > 2.6.14 patches there in the source directory now).  So, any hope of
>  > seeing this filter down into FC4 eventually?

> I had this idea a while back to increase the testing that usptream -rc
> kernels get, by pushing them out to updates-testing.  It's something
> that sounds great on paper, but in reality would be a total disaster.

> 2.6.14rc2 doesn't even boot on half my test boxes right now, and from
> the feedback from folks at the office and bugzilla, it's pretty grim
> and nowhere near ready for general consumption.

> 2.6.13 was pretty much the same way. For quite a few people, it was
> unusable without the PCI fixes that went into 2.6.13.1

> I've cooked up a 2.6.13.2 test kernel that I'll be pushing out to
> fc4-updates-testing in the next few hours. It'll likely need
> quite a bit more work before its ready for updates-final too,
> but it gives people something to play with until its ready.

	Sooner I can lay my hands on that the better.  I need to roll this
usb-cdc-acm performance patch into that and get it on a box with several
ISDN modems.  The whole upgrade to 2.6.14rc2 seems to be a real mess
(re: thread I'm in the middle of over on fedora-devel over the kudzu
catch-22).  As soon as that's available, I'll try giving it a hammering.

> 		Dave

	One BIG question...

	This is vis-a-vis the kudzu conflict vs 2.6.13 kernels being beat on
over on the fedora-devel list.  On what side of the fence will this
2.6.13.2 kernel fall?  Does it conflict with the kudzu currently with
the 2.6.12 kernels?  Will this 2.6.13.2 kernel provide us with a
stepping stone past the kernel <-> kudzu catch-22 critical dependency?
The 2.6.13-1.1567 kernel (which is really the 2.6.14rc2 kernel)
conflicts with the existing kudzu.  The kudzu from rawhide conflicts
with any kernel < 2.6.13.  Sooo...  Is it real or is it memorex?  Is it
really < 2.6.13 or is it really < 2.6.14rc2?  What happens in the
boundary condition we appear to be approaching?

	Mike
-- 
 Michael H. Warfield    |  (770) 985-6132   |  mhw WittsEnd com  
  /\/\|=mhw=|\/\/       |  (678) 463-0932   |  http://www.wittsend.com/mhw/
  NIC whois:  MHW9      |  An optimist believes we live in the best of all
 PGP Key: 0xDF1DD471    |  possible worlds.  A pessimist is sure of it!

Attachment: signature.asc
Description: This is a digitally signed message part


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]