public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Padfoot <padfoot@exemail.com.au>
To: linux-kernel@vger.kernel.org
Subject: [DEVICE SUPPORT] Atheros 0cf3:e019
Date: Sat, 11 Feb 2012 13:27:58 +1100	[thread overview]
Message-ID: <4F35D22E.3000303@exemail.com.au> (raw)
In-Reply-To: <4F35B0A1.5090705@exemail.com.au>

Hi,

Apologies for posting twice. Please see the below email sent to 
linux-bluetooth list on 2 Feb. Yet to receive a response. Most likely 
the bluetooth team are flat out with other issues ATM.

Hopefully someone here may be able to assist.

Thanks.
Lachlan.

-------- Original Message --------
Subject: 	[DEVICE SUPPORT] Atheros 0cf3:e019
Date: 	Thu, 02 Feb 2012 19:34:20 +1100
From: 	Padfoot <padfoot@exemail.com.au>
Reply-To: 	padfoot@exemail.com.au
To: 	linux-bluetooth@vger.kernel.org



Hi,

I am trying to find out the state of support in the linux bluetooth
stack for devices reporting as Atheros VID 0cf3 PID e019.

I am using Arch Linux binary kernel 3.2.2 64 bit.

The device is recognised and appropriate modules loaded without error,
yet trying to access bluetooth I am told no adapter is present.

Output of lsmod | grep ath
$ lsmod | grep ath
ath9k                  87343  0
ath9k_common            2096  1 ath9k
ath9k_hw              347282  2 ath9k_common,ath9k
ath                    14802  3 ath9k_hw,ath9k_common,ath9k
mac80211              228367  1 ath9k
cfg80211              172260  3 mac80211,ath,ath9k

Output of lsmod | grep bt
]$ lsmod | grep bt
btusb                  11385  1
bluetooth             151999  13 btusb,bnep,rfcomm
usbcore               146241  9
ehci_hcd,ohci_hcd,usbhid,usb_storage,ums_realtek,uvcvideo,uas,btusb

Output of lsusb -v
Bus 005 Device 003: ID 0cf3:e019 Atheros Communications, Inc.
Device Descriptor:
   bLength                18
   bDescriptorType         1
   bcdUSB               1.10
   bDeviceClass          224 Wireless
   bDeviceSubClass         1 Radio Frequency
   bDeviceProtocol         1 Bluetooth
   bMaxPacketSize0        64
   idVendor           0x0cf3 Atheros Communications, Inc.
   idProduct          0xe019
   bcdDevice            0.01
   iManufacturer           0
   iProduct                0
   iSerial                 0
   bNumConfigurations      1

Thanks.
Lachlan.


       reply	other threads:[~2012-02-11  2:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F35B0A1.5090705@exemail.com.au>
2012-02-11  2:27 ` Padfoot [this message]
     [not found] <E1Rw0SU-0005n1-Io@smtp.po.exetel.com.au>
2012-02-11 20:01 ` [DEVICE SUPPORT] Atheros 0cf3:e019 Padfoot

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=4F35D22E.3000303@exemail.com.au \
    --to=padfoot@exemail.com.au \
    --cc=linux-kernel@vger.kernel.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