From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] SDIO support
Date: Wed, 13 Feb 2008 14:45:05 +0100 [thread overview]
Message-ID: <1202910306.7664.413.camel@violet> (raw)
In-Reply-To: <5976F853A3B35845B6375F0C1FE13EB30315351E@hasmsx415.ger.corp.intel.com>
Hi Claudio,
> Does anybody know about an SDIO specific device tested with BlueZ stack?
> Any modifications required to the generic driver?
I have the Socket SDIO card and that one works perfectly fine. It is a
Type-B card, but we switch it back into Type-A mode. We don't need
anything else than Type-A since we have a full Bluetooth stack running
anyway.
http://www.holtmann.org/linux/bluetooth/sdio.html
The Socket SDIO actually contains a Bluetooth chip from Toshiba.
I also have done initial tests with the BlueCore6 from CSR. The
BlueCore6 contains a native SDIO interface. My prototype is still
crashing and I never got a newer one. Hint :)
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-02-13 13:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 16:08 [Bluez-users] SDIO support Glickman, Claudio
2008-02-08 16:23 ` Marcel Holtmann
2008-02-13 13:16 ` Glickman, Claudio
2008-02-13 13:45 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-12 22:28 Mirza Baig
2006-07-12 23:23 ` Marcel Holtmann
2006-07-13 0:07 ` Mirza Baig
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=1202910306.7664.413.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/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