| |||||||||||||
|
| |||||||||||||
Cannot stay at 2.6.16.x because...Cannot stay at 2.6.16.x because...Posted Mar 12, 2007 19:32 UTC (Mon) by pr1268 (subscriber, #24648)In reply to: Stable kernel 2.6.20.2 by ahoogerhuis Parent article: Stable kernel 2.6.20.2
I can't stay at 2.6.16.x with my laptop - Broadcom bcm43xx needed for my wifi card. If I remember correctly, 2.6.17 was the first to include in-kernel driver support for this chipset. Which brings me to this question: Why is 2.6.16.x getting a bunch of bugfix updates (they're up to 2.6.16.43 now!)? Any reason 2.6.17 didn't get these bugfixes?
(Log in to post comments)
bcm43xx Posted Mar 12, 2007 19:43 UTC (Mon) by ncm (subscriber, #165) [Link] bcm43xx support is *almost there*. I still have to load bcm43xx_d80211 and unload it, before loading bcm43xx, in order to get any contact with my ddWRT hub. Looking at the patches, it's amazing how much chip-version fiddling the code has to do to make these things work at all. I'd have thought that with Broadcom actively cooperating there would be less churn.
bcm43xx Posted Mar 13, 2007 16:30 UTC (Tue) by proski (subscriber, #104) [Link] It would be great if you post the details to the bcm43xx mailing list (bcm43xx-dev at lists.berlios.de).
Cannot stay at 2.6.16.x because... Posted Mar 13, 2007 5:45 UTC (Tue) by dlang (✭ supporter ✭, #313) [Link] a maintainer stepped up and decided to commit to patching 2.6.16 long-term.
nobody has done this for later versions
Cannot stay at 2.6.16.x because... Posted Mar 13, 2007 9:00 UTC (Tue) by tomas2 (guest, #37038) [Link] "a maintainer stepped up and decided to commit to patching 2.6.16 long-term."
AFAIK it's Adrian Bunk.
I thought back then when I first read about this that Debian would go with this kernel for Etch, but they didn't. Anyone knows why?
Tomas
|
|
||||||||||||