public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Kyler Laird <Kyler@Lairds.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] What Bluetooth CF cards do developers use?
Date: Wed, 28 Apr 2004 08:56:04 -0500	[thread overview]
Message-ID: <20040428135604.GD1862@snout> (raw)

So far I've bought three CF cards to use with BlueZ.  The first wasn't
supported well at all.  The second set (Socket, without a protruding
antenna) was slick but doesn't work with BlueZ under Linux 2.6.

I want to get something that will work under 2.6 and is likely to
continue working for awhile (so that I don't have to convince my boss
to keep buying new ones).  I suspect that the best way to do that is to
get whatever the developers use.

So...what's a good choice?  I'd especially like to find something that
will readily work with the Zaurus.  A product that is readily available
at Best Buy/Circuit City/... is preferred.

Thank you.

--kyler



-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2004-04-28 13:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-28 13:56 Kyler Laird [this message]
2004-04-28 14:09 ` [Bluez-devel] What Bluetooth CF cards do developers use? Marcel Holtmann
2004-04-28 14:16   ` Kyler Laird
2004-04-28 14:23     ` Marcel Holtmann
2004-04-29 18:13       ` Kyler Laird
2004-04-29 19:05         ` Marcel Holtmann
2004-04-29 19:20           ` Kyler Laird

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=20040428135604.GD1862@snout \
    --to=kyler@lairds.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox