From: Johannes Berg <johannes@sipsolutions.net>
To: Pavel Roskin <proski@gnu.org>
Cc: "Larry Finger" <Larry.Finger@lwfinger.net>,
"Rafał Miłecki" <zajec5@gmail.com>,
b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: Broadcom card totally not visible for system (lspci)
Date: Tue, 30 Mar 2010 21:29:23 +0200 [thread overview]
Message-ID: <1269977363.3927.26.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1269975753.4938.8.camel@mj>
On Tue, 2010-03-30 at 15:02 -0400, Pavel Roskin wrote:
> On Tue, 2010-03-30 at 12:48 -0500, Larry Finger wrote:
> > On 03/30/2010 12:31 PM, Rafał Miłecki wrote:
> > >
> > > Is this possible it's disabled in BIOS by default and needs execution
> > > of some ACPI command or sth to make it work?
> > >
> > > Yeah, trying to find some other reason than faulty WiFi... It's weird
> > > it was working fine "before a moment" on Windows.
> >
> > Winblows can fiddle with the "Wake-on-LAN" setting in the BIOS, but AFAIK, the
> > BCM4306 does not have this capability. If the BIOS has that setting, it should
> > be turned off.
>
> Perhaps it's a crazy idea, but what if the Ethernet device and the WiFi
> device are connected to the same SSB bus, an thus sharing the PCI ID?
Should be fine, actually, since b43 binds the 802.11 ssb core.
johannes
next prev parent reply other threads:[~2010-03-30 19:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 16:56 Broadcom card totally not visible for system (lspci) Rafał Miłecki
2010-03-30 17:19 ` Larry Finger
2010-03-30 17:31 ` Rafał Miłecki
2010-03-30 17:48 ` Larry Finger
2010-03-30 19:02 ` Pavel Roskin
2010-03-30 19:06 ` Rafał Miłecki
2010-03-30 19:41 ` Pavel Roskin
2010-03-30 19:29 ` Johannes Berg [this message]
2010-03-31 6:39 ` Holger Schurig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1269977363.3927.26.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.org \
--cc=zajec5@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).