From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] first(?) bc4 module
Date: Wed, 13 Apr 2005 11:31:09 +0200 [thread overview]
Message-ID: <1113384669.9061.8.camel@pegasus> (raw)
In-Reply-To: <425C13CB.1060605@xmission.com>
Hi Brad,
> socketcom is claiming their bc4 (class 1) module is shipping this month.
> it's a good sign for eventually getting it in consumer gear.
may you also wanna look at Taiyo Yuden, because according to the
qualification listing they also have a BlueCore4 based module.
> if samples aren't too hard to come by, i'll try to wire one up to a
> gumstix. (gumstix is sending me a sample)
Try to convince them to donate one to me, then I can try that out with
attaching a Casira to it. However in general the UARTs are too slow for
the EDR transfer rates.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-04-13 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 18:30 [Bluez-devel] first(?) bc4 module Brad Midgley
2005-04-13 9:31 ` Marcel Holtmann [this message]
2005-04-14 15:16 ` Brad Midgley
2005-04-14 16:03 ` Marcel Holtmann
2005-04-14 16:26 ` Peter Wippich
2005-04-14 17:02 ` Marcel Holtmann
2005-04-14 17:25 ` Peter Wippich
2005-04-14 17:36 ` Marcel Holtmann
2005-04-14 18:22 ` Peter Wippich
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=1113384669.9061.8.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.