From: Brad Midgley <bmidgley@xmission.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] SCO and broadcom devices
Date: Fri, 30 Sep 2005 16:55:41 -0600 [thread overview]
Message-ID: <433DC26D.9040406@xmission.com> (raw)
In-Reply-To: <1128069869.8762.6.camel@dist>
Preben,
Sorry... no one is working on broadcom sco and no one has detailed docs
anyway as far as I know.
Brad
Preben Holm wrote:
> Hi everyone,
>
> Will there be any support for SCO in the near future of broadcom
> devices?
> I won't go buy a cellink, if the support is on it's way!
>
> Btw. my broadcom device works with the standard drivers hci_usb!
>
> An lsusb gives this:
> ID Broadcom 0a5c:200a Broadcom Corp.
>
>
> Thanks for your help!
>
> / Preben
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-09-30 22:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 17:42 [Bluez-users] Problem with bluetooth sound... working but not working Preben Holm
2005-09-28 22:21 ` Andreas Beck
2005-09-30 8:44 ` [Bluez-users] SCO and broadcom devices Preben Holm
2005-09-30 22:55 ` Brad Midgley [this message]
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=433DC26D.9040406@xmission.com \
--to=bmidgley@xmission.com \
--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 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.