From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Porting bluez onto different embedded systems
Date: Fri, 02 Dec 2005 14:01:15 +0100 [thread overview]
Message-ID: <1133528475.20834.46.camel@blade> (raw)
In-Reply-To: <20051202121947.73018.qmail@web36108.mail.mud.yahoo.com>
Hi Swathi,
> I doing research on porting the powerful bluetooth stack, bluez onto
> different embedded systems. I went through the questions which were
> being asked on porting bluez onto different embedded systems. Some of
> the developers have said it is possible to port bluez onto different
> platforms but it involves a lot of modifications have to be done. Can
> someone provide me with useful links or informations which will be
> helpful in porting bluez onto different OS.
> All the comments are welcome as it will be helpful in doing my
> research.
I think that it is badly spent time even trying to port it. Everything
of BlueZ inside the kernel is fully kernel specific and the Bluetooth
library depends on the interfaces offered by the Bluetooth subsystem
inside the kernel. However feel free to try porting it, but keep in mind
the every line of code is GPL and that any port must be GPL, too.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-12-02 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 12:19 [Bluez-users] Porting bluez onto different embedded systems Swathi Mathur80
2005-12-02 13:01 ` 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=1133528475.20834.46.camel@blade \
--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;
as well as URLs for NNTP newsgroup(s).