From: "ct cwgt" <ct.cwgt@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] bluez from the ground up?
Date: Sat, 16 Feb 2008 22:53:46 -0500 [thread overview]
Message-ID: <e34b02f0802161953q5c9cd905l8c9d27cf917e4e91@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 768 bytes --]
hello all,
i am wondering if anyone can help me compile a complete list of kernel
modules and packages required to get bluez running using a usb BT dongle
under a 2.6 kernel.
i know such a request may seem a bit odd but, i'm finding myself in a
position where i'm being bitten by the automagical nature of linux package
managers which handle dependencies. i've been tasked with sorting a bluez
under a custom linux distro and am seeking assistance/advice on packages i
can manually add/configure to support the use of a USB dongle.
if anyone can point me toward documentation to help me with this task, i
would appreciate it. as well, i'd like to compile this information with the
hope of creating a distro agnostic bluez troubleshooting guide.
thanks in advance!
[-- Attachment #1.2: Type: text/html, Size: 814 bytes --]
[-- Attachment #2: Type: text/plain, Size: 228 bytes --]
-------------------------------------------------------------------------
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/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2008-02-17 3:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 3:53 ct cwgt [this message]
2008-02-19 20:45 ` [Bluez-users] bluez from the ground up? Marcel Holtmann
2008-02-19 23:42 ` ct cwgt
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=e34b02f0802161953q5c9cd905l8c9d27cf917e4e91@mail.gmail.com \
--to=ct.cwgt@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox