public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Wiebe Baron <Wiebe.Baron@Wirelessvalue.nl>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Embedded bluetooth recommendations
Date: Mon, 25 Oct 2004 10:44:19 +0200	[thread overview]
Message-ID: <1098693859.24932.18.camel@pegasus> (raw)
In-Reply-To: <006201c4ba6b$d39682e0$a900a8c0@wivd10>

Hi Wiebe,

> I have a question about embedded Bluetooth. I'm working on a feedback
> control project which involves 8 devices. Up till now a module has
> been used with integrated stack but this is unable to support an
> RFCOMM link with seven slaves and the response time of a scatternet is
> unacceptable so I'm now looking for a multiprocessor solution with a
> separate stack. 

are you talking about seven RFCOMM links on the same ACL link or about
seven different ACL links. If you really wanna work with piconet where
the master controls 7 slaves you should use a CSR chip, because all
other Bluetooth chips are acting somekind weird. However even with the
CSR stuff you must make sure that at least a HCI 18.2 firmware is used.

> I'm currently experimenting with a sharp LH79520 with embedded Linux
> from metrowerks and Bluez but this seems to be overkill because the
> application requirements themselves are minimal (7 way cable
> replacement).

The Sharp uses an ARM7TDMI. Actually this is really overkill and then
you should better buy a Bluetooth chip that itself uses this ARM chip
like Zeevo etc. However then the above point comes in ...

> Does anyone have a suggestion of a combination of stack, operating
> system and microprocessor that is known to work together and has
> minimum requirements in terms of RAM, ROM and processor speed (cost)?

I am not a microprocessor expert, but actually every processor with
Linux support should be useable and BlueZ is of course the best choice
for a Bluetooth stack.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-10-25  8:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-25  8:22 [Bluez-users] Embedded bluetooth recommendations Wiebe Baron
2004-10-25  8:44 ` Marcel Holtmann [this message]
2004-10-28 10:27   ` Wiebe Baron
2004-10-28 10:47     ` 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=1098693859.24932.18.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=Wiebe.Baron@Wirelessvalue.nl \
    --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