From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] USB drivers & architecture
Date: Thu, 03 Feb 2005 22:24:52 +0100 [thread overview]
Message-ID: <1107465892.6911.3.camel@pegasus> (raw)
In-Reply-To: <008c01c50a35$c68c11e0$0100a8c0@hppav>
Hi Oliver,
> I am new in the list and I hope I am not making a rethorical
> question,
>
> I am looking at the linux source code and the architecture of BlueZ on
> the website.
>
> I can see that in the folder /net/bluetooth/* there is the
> implementation of the layers HCI and L2CAP
>
> Inside there is some foldwers like /bnep /rfcoom /hidp... which are
> layers on the top of L2CAP
>
> The blueZ libs bring us the API to acces these last layers....
>
> At this point if I am wong, I beg for a correction.
everything is fine so far.
> So my question is, where are the sources for the physical layers?
> Where can I the drivers for the USB dongles etc?
Look at drivers/bluetooth/ for the host transport drivers.
> What is exactily what I found in /drivers/usb/classa/bluetty ?
It is an old driver that converts a Bluetooth H:2 dongle into a
Bluetooth serial device with H:4 protocol.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-02-03 21:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 21:17 [Bluez-devel] USB drivers & architecture Oliver
2005-02-03 21:24 ` 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=1107465892.6911.3.camel@pegasus \
--to=marcel@holtmann.org \
--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.