On Sat, Feb 23, 2008 at 2:24 PM, Ingo Molnar <[EMAIL PROTECTED]> wrote: > > * Pekka Enberg <[EMAIL PROTECTED]> wrote: > > > Agreed. Alexey, did you identify a specific git commit that caused the > > regression? Can we just revert that from 2.6.24? Michael, even if > > _you're_ planning to remove bcm43xx we must not let it regress until > > it's gone. > > btw., if the best answer is: "do not enable b43 and bcm43xx at once in > the .config because we messed up the dependencies and fixing it in > 2.6.24-stable is unfortunately too risky", then that's a perfectly fine > answer for -stable. Then the fix would be to exclude each other in the > Kconfig space (which is not risky). But just ignoring bugreports and > NAK-ing a fix is not a valid answer. >
The problem is not with enabling both b43 and bcm43xx (will, whis won't work anyway, and there is no chance fixing it). The problem is with enabling the bcm43xx wifi driver and the b44 Ethernet driver. The ethernet driver then wrongly autosolects some config options that prevent the bcm43xx driver from loading, so I'm left with either no wifi or no ethenet. > Ingo > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
