lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 23 Feb 2008 14:51:43 +0300
From:	"Alexey Zaytsev" <alexey.zaytsev@...il.com>
To:	"Pekka Enberg" <penberg@...helsinki.fi>
Cc:	"Ingo Molnar" <mingo@...e.hu>, "Michael Buesch" <mb@...sch.de>,
	"Alexey Zaytsev" <zaytsev.a@...tei.ru>, "Greg KH" <greg@...ah.com>,
	linux-kernel@...r.kernel.org,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>
Subject: Re: bcm43xx regression in 2.6.24 (with patch)

On Sat, Feb 23, 2008 at 2:37 PM, Pekka Enberg <penberg@...helsinki.fi> wrote:
> On Sat, Feb 23, 2008 at 1:32 PM, Alexey Zaytsev
>  <alexey.zaytsev@...il.com> wrote:
>  >  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.
>
>  So does reverting commit 753f492093da7a40141bfe083073400f518f4c68
>  ("[B44]: port to native ssb support") fix the regression?
>

Compiling it right now.

I'm sure it fixes the problem, but I don't feel like we should revert
it. I can't
be sure it won't cause any other problems, and anyway, this does not look
right a solution. Any other driver (rightfully) requiring the SSB_HOST would
then also break the bcm43xx driver.

I'll send an simplified patch in a few minutes.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists