From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco: Not working...but almost
Date: Fri, 11 Nov 2005 15:28:44 -0700 [thread overview]
Message-ID: <43751B1C.4060600@xmission.com> (raw)
In-Reply-To: <437514D5.7040300@gmx.de>
Maik
> Any chance to get these supported? Using an additional USB Bluetooth
> stick when I have a built-in adapter seems stupid.
I looked into finding technical docs from another vendor for the same
problem (integrated bluetooth adapter not csr) but didn't get very far.
If you can find technical docs, maybe it's not that bad to add support.
I don't know, but without docs the point is moot.
Maybe you don't like the usb adapter for the same reason I don't. I
really hated the idea of putting a usb dongle on my laptop that could
get knocked off or forgotten when I was packing up. So the socketcom cf
adapter was attractive since it doesn't protrude. I don't have it any
more and I can't remember offhand if I tried sco in linux. Surely
someone on the list could tell us.
Brad
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-11-11 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 22:01 [Bluez-devel] btsco: Not working...but almost Maik Zumstrull
2005-11-11 22:28 ` Brad Midgley [this message]
2005-11-12 13:38 ` Maik Zumstrull
2005-11-12 13:41 ` Marcel Holtmann
2005-11-12 14:02 ` Maik Zumstrull
2005-11-12 14:22 ` Marcel Holtmann
2005-11-12 14:29 ` Maik Zumstrull
2005-11-12 14:54 ` [Bluez-devel] btsco: It works! Maik Zumstrull
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=43751B1C.4060600@xmission.com \
--to=bmidgley@xmission.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 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.