From: "Gábor Stefanik" <netrolller.3d@gmail.com>
To: b43-dev@lists.infradead.org
Subject: [14e4:4315] Dell Studio 1735, rfkill problem
Date: Sat, 24 Apr 2010 05:09:43 +0200 [thread overview]
Message-ID: <i2p69e28c911004232009i84a28bc1na652709264b1b005@mail.gmail.com> (raw)
In-Reply-To: <4BD25D60.5000007@lwfinger.net>
2010/4/24 Larry Finger <Larry.Finger@lwfinger.net>:
> On 04/23/2010 07:03 PM, G?bor Stefanik wrote:
>>
>> Looks like I got lpphy_op_software_rfkill wrong then.
>>
>> Larry, is the spec up to date on this matter?
>>
>
> The rfkill switch behaves just as expected on my machine. When I switch
> it off, I get the expected message in the log. When turned on, again the
> expected message, and it connects as expected.
>
> The OPs machine generates the on/off messages in b43. I do not think b43
> is responsible for not connecting.
>
> I have seen nothing in the specs about the rfkill mechanism. I'm not
> even certain that Broadcom implements it.
AFAIK it isn't called "rfkill" in the specs, but "enable/disable radio".
>
> Larry
>
>
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
next prev parent reply other threads:[~2010-04-24 3:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 22:05 [14e4:4315] Dell Studio 1735, rfkill problem Григорий Фучеджи
2010-04-23 22:21 ` Gábor Stefanik
[not found] ` <w2rb7f967271004231625pf533c5f9l82a5bd19f31c7355@mail.gmail.com>
2010-04-23 23:30 ` Grygoriy Fuchedzhy
2010-04-24 0:03 ` Gábor Stefanik
2010-04-24 2:54 ` Larry Finger
2010-04-24 3:09 ` Gábor Stefanik [this message]
[not found] ` <20100424110940.2b908933@laptop.homenet>
[not found] ` <20100424112652.28e5735a@laptop.homenet>
2010-04-24 11:35 ` Grygoriy Fuchedzhy
2010-04-24 14:05 ` Larry Finger
2010-04-24 16:22 ` Chris Vine
2010-04-26 21:03 ` Grygoriy Fuchedzhy
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=i2p69e28c911004232009i84a28bc1na652709264b1b005@mail.gmail.com \
--to=netrolller.3d@gmail.com \
--cc=b43-dev@lists.infradead.org \
/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).