From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Running L2CAP & HCI layers without OS
Date: Tue, 22 Feb 2005 11:00:07 +0100 [thread overview]
Message-ID: <1109066407.8506.11.camel@pegasus> (raw)
In-Reply-To: <20050222092538.81728.qmail@web53205.mail.yahoo.com>
Hi Filipa,
> It seams that my question about the l2cap and hci
> layers implemented in User Space is not so stupid
> after all! ;)
you should spent some time to think about hardware abstraction and the
right interface to L2CAP, RFCOMM etc. and then this looks stupid again.
Actually the OpenBT Bluetooth stack had exactly these two problems.
> Could anyone give me directions on how to run these
> layers without OS? One solution, I think, would be to
> change the l2cap and the hci files in order on not to
> have any OS call (that was actually what I as doing,
> which is quite a heavy work!). But it seams that there
> is an easy way (thanks Marcel, for pointing that
> out!).
There is no easy way and actually I don't see any need for it. Feel free
to start another Bluetooth stack, but this mailing list is about the
BlueZ and Linux and not any other operating system.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-02-22 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 9:25 [Bluez-users] Running L2CAP & HCI layers without OS Filipa Duarte
2005-02-22 10:00 ` Marcel Holtmann [this message]
2005-02-22 15:14 ` Filipa Duarte
2005-02-22 15:25 ` Marcel Holtmann
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=1109066407.8506.11.camel@pegasus \
--to=marcel@holtmann.org \
--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