Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Newbie:) Is it a good suit for Embedded Linux OS
Date: Wed, 11 Jan 2006 15:31:12 +0100	[thread overview]
Message-ID: <1136989872.3825.32.camel@localhost.localdomain> (raw)
In-Reply-To: <20060111023702.65726.qmail@web34012.mail.mud.yahoo.com>

Hi,

> This will be my first question on Bluez. There is so much of hype
> about bluez ?
> I am a chinese student who is doing research on comparing which is the
> best bluetooth stack for embedded Linux ? do you think guys it is the
> bluez, if so can anyone tell me the reason 

yes it is. See the WideRay stuff, TomTom GO series or Nokia 770 for real
productive examples running BlueZ.

> 2. How much memory required to run the bluetooth module on the
> embedded linux ?

The footprint is actually rather small. However it depends on your
architecture. Simply cross-compile and look at the modules or binary
sizes.

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

      reply	other threads:[~2006-01-11 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11  2:37 [Bluez-users] Newbie:) Is it a good suit for Embedded Linux OS Wai Jye Chang
2006-01-11 14:31 ` 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=1136989872.3825.32.camel@localhost.localdomain \
    --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