From: Marcel Holtmann <marcel@holtmann.org>
To: Kutschenreuter Matthias <Matthias.Kutschenreuter@siemens.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hciattach killed
Date: Wed, 03 Mar 2004 16:04:11 +0100 [thread overview]
Message-ID: <1078326250.2787.128.camel@pegasus> (raw)
In-Reply-To: <AFE91B59A185A5439840B43AB79190470938E8@mchp997a.mch.sbs.de>
Hi Matthias,
> we use the latest available bluez-modules on a 2.4.21
> kernel with the latest available patch.
my fault. I meant what kind of Bluetooth module do you use?
> OK, we did some changes in the hciattach, because we do
> weired things like attaching a BT Chip that has no EPROM.
> so we have to tell the device its MAC address with
> "hciattach ttyS0 <special> 115200 <MAC>"
>
> But we think, the Ctrl-C problem isnt due to our changes,
> we only adapted the initialisation of the chip, like demanded
> by the chip.
Show us the code and we will see what you have done. If you really
changed so much then go back and try it with a standard Bluetooth module
and see if it also shows the same problems.
Regards
Marcel
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next parent reply other threads:[~2004-03-03 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AFE91B59A185A5439840B43AB79190470938E8@mchp997a.mch.sbs.de>
2004-03-03 15:04 ` Marcel Holtmann [this message]
[not found] <AFE91B59A185A5439840B43AB79190470938E7@mchp997a.mch.sbs.de>
2004-03-03 14:10 ` [Bluez-devel] hciattach killed Marcel Holtmann
2004-03-03 13:21 Kutschenreuter Matthias
2004-03-03 13:32 ` 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=1078326250.2787.128.camel@pegasus \
--to=marcel@holtmann.org \
--cc=Matthias.Kutschenreuter@siemens.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox