From: Marcel Holtmann <marcel@holtmann.org>
To: gonzalo briceno <gonzaloother@yahoo.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Re: Bluez setup and Bluetooth stack and 2.6 kernel
Date: Thu, 26 Aug 2004 16:33:28 +0200 [thread overview]
Message-ID: <1093530808.2581.30.camel@pegasus> (raw)
In-Reply-To: <20040826141810.46943.qmail@web52608.mail.yahoo.com>
Hi Gonzalo,
> So what I gather is that the bluez.o module
> functionality is already part of the bluetooth.ko
> module. Is there anything else I need to know in
> terms of what modules need to be loaded for things to
> work? The reason for asking is that most
> documentation I have read so far is most likely old
> and refers to bluez.o. To make a long story short
> does the following seem correct to get USB and
> Bluetooth to work (using kernel 2.6) barring any other
> problems:
>
> 1. load usbcore
> 2. load proper USB host driver (OHCI, UHCI, EHCI)
> 3. load bluetooth.ko
> 4. load (RFCOMM, L2CAP, BNEP, etc)
this is correct, but you can leave step 1 and 3 out, because the module
dependency will take of that these are also loaded. However you forgot
the Bluetooth hardware driver. In general this is the hci_usb driver for
the H:2 transport protocol support.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-08-26 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 14:18 [Bluez-users] Re: Bluez setup and Bluetooth stack and 2.6 kernel gonzalo briceno
2004-08-26 14:33 ` Marcel Holtmann [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=1093530808.2581.30.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=gonzaloother@yahoo.com \
/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