linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: rfkill on T61
Date: Thu, 11 Jun 2009 17:13:12 -0700	[thread overview]
Message-ID: <43e72e890906111713q338c178ah34d263db43693c58@mail.gmail.com> (raw)
In-Reply-To: <1244765167.27395.1.camel@violet>

On Thu, Jun 11, 2009 at 5:06 PM, Marcel Holtmann<marcel@holtmann.org> wrote:
> Hi Luis,
>
>> >> When I hit rfkill, I get:
>> >>
>> >> [18493.777231] btusb_intr_complete: hci0 urb cbe20000 failed to resubmit (19)
>> >> [18493.777553] btusb_send_frame: hci0 urb f7d3c700 submission failed
>> >>
>> >> When I hit it again I get:
>> >>
>> >> [18531.488091] usb 1-1: new full speed USB device using uhci_hcd and address 7
>> >> [18531.651409] usb 1-1: configuration #1 chosen from 1 choice
>> >>
>> >> The device that disappears upon rfkill is my bluetooth controller:
>> >>
>> >> mcgrof@tesla ~ $ diff -u before-rfkill after-rfkill
>> >> --- 1   2009-06-11 15:37:37.000000000 -0700
>> >> +++ 2   2009-06-11 15:37:49.000000000 -0700
>> >> @@ -6,7 +6,6 @@
>> >>  Bus 003 Device 004: ID 046d:c040 Logitech, Inc. Corded Tilt-Wheel Mouse
>> >>  Bus 003 Device 003: ID 04b3:4485 IBM Corp.
>> >>  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> >> -Bus 001 Device 006: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller
>> >>  Bus 001 Device 004: ID 0483:2016 SGS Thomson Microelectronics
>> >> Fingerprint Reader
>> >>  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> >>  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> >>
>> >> Granted I tested this on 2.6.27 with bleeding edge compat-wireless but
>> >> I think this is the same behaviour I will get with bleeding edge, will
>> >> try now on wireless-testing.
>> >
>> > what are you trying to tell us.
>>
>> my 802.11 device is not rfkill'ed on the T61, some patches recently
>> went in to add support for rfkill on ath5k. I do have thinkpad_acpi
>> loaded on this ancient 2.6.27 kernel.
>>
>> I'll try on wireless-testing next, build is almost done.
>
> still are not getting what you wanna tell us. What has Bluetooh RFKILL
> switch to do with WiFi.

Nothing, I really was just unaware we rfkilled bluetooth as well. Plus
like I said my 802.11 device is not being rfkilled, which is what I
actually did expect.

> With an updated mac80211/cfg80211 the soft kill
> should work for every mac80211 based driver. Works for me with iwlwifi
> in my X200.

I see, thanks, not sure what soft rfkill is so will go read the docs.

  Luis

  reply	other threads:[~2009-06-12  0:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11 22:59 rfkill on T61 Luis R. Rodriguez
2009-06-11 23:32 ` Marcel Holtmann
2009-06-11 23:59   ` Luis R. Rodriguez
2009-06-12  0:06     ` Marcel Holtmann
2009-06-12  0:13       ` Luis R. Rodriguez [this message]
2009-06-12  0:20         ` Luis R. Rodriguez
2009-06-12  0:22           ` Luis R. Rodriguez
2009-06-12  1:27             ` William Keaney
2009-06-12  7:51               ` Luis R. Rodriguez
2009-06-12 13:11                 ` Gábor Stefanik

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=43e72e890906111713q338c178ah34d263db43693c58@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcel@holtmann.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).