From: Graham Burnside <graham@somethingshocking.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: ralink rt3290/3298 pcie
Date: Wed, 20 Mar 2013 21:02:01 +0000 [thread overview]
Message-ID: <514A23C9.1040304@somethingshocking.com> (raw)
In-Reply-To: <201303202253.21510.oliver@neukum.org>
On 20/03/13 21:53, Oliver Neukum wrote:
> Am Mittwoch, 20. März 2013, 20:39:56 schrieb Graham Burnside:
>
>> hciconfig gives no ouput.
>>
>> The directory /sys/kernel/debug/usb/devices does not exist. I'm not sure
>> what else might be useful?
>>
>>
>> Here is the relevant output from lspci -v (note there is no kernel
>> driver being loaded for the bluetooth device).
>>
>> 01:00.0 Network controller: Ralink corp. Device 3290
>> Subsystem: Hewlett-Packard Company Device 18ec
>> Flags: bus master, fast devsel, latency 0, IRQ 16
>> Memory at c2510000 (32-bit, non-prefetchable) [size=64K]
>> Capabilities: [40] Power Management version 3
>> Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
>> Capabilities: [70] Express Endpoint, MSI 00
>> Capabilities: [100] Advanced Error Reporting
>> Capabilities: [140] Device Serial Number 00-00-4d-fa-a8-23-94-68
>> Kernel driver in use: rt2800pci
>>
>> 01:00.1 Bluetooth: Ralink corp. Device 3298
>> Subsystem: Hewlett-Packard Company Device 18ec
>> Flags: bus master, fast devsel, latency 0, IRQ 11
>> Memory at c2500000 (32-bit, non-prefetchable) [size=64K]
>> Capabilities: [40] Power Management version 3
>> Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
>> Capabilities: [70] Express Endpoint, MSI 00
>> Capabilities: [100] Advanced Error Reporting
>> Capabilities: [140] Device Serial Number 00-00-4e-fa-a8-23-94-68
>
> The device is indeed PCI and different to anything else in the world.
> It doesn't use the normal HC commands. The registers are not documented.
> I am afraid you are out of luck with this device.
>
> Regards
> Oliver
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Thanks for the feedback.
I guess I'm at the mercy of ralink.
I noticed there is another ralink combo chip (5390). Is this also
lacking support?
If anyone is interested I came across this driver, from the system
builder zotac,
http://downloads.zotac.com/mediadrivers/mb/download/NB087_Ubuntu.zip
- Graham
--
Get my public signing / encryption OpenPGP key at:
https://www.somethingshocking.com/grahamPublicPGP.key
next prev parent reply other threads:[~2013-03-20 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <514A09AD.20809@somethingshocking.com>
2013-03-20 19:39 ` ralink rt3290/3298 pcie Graham Burnside
2013-03-20 21:53 ` Oliver Neukum
2013-03-20 21:02 ` Graham Burnside [this message]
2013-03-19 22:48 Graham Burnside
2013-03-20 16:58 ` Gustavo Padovan
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=514A23C9.1040304@somethingshocking.com \
--to=graham@somethingshocking.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=oliver@neukum.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