public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Bitterlich Jean-Yves ICM MP PD TI 10 <jean-yves.bitterlich@siemens.com>
Cc: "'bluez-devel@lists.sourceforge.net'"
	<bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] dumping/debuging ttySX ...
Date: Fri, 27 Feb 2004 12:47:23 +0100	[thread overview]
Message-ID: <1077882443.2843.27.camel@pegasus> (raw)
In-Reply-To: <0E67B9FA7DC6B24391C00208804C1E552C2D25@mchh9ena.mchh.siemens.de>

Hi Jean-Yves,

> I'm currently adapting bluez to run a bt chip via uart. it seems that
> modifying hciattach initialization code might be enough. however i'm having
> trouble after initialization whenever the driver take the socket over
> (N_HCI). for some reason, the chip sends lots of "invalid packet events" and
> "startup events".
> 
> before going further, i need to know what is sent over uart (i.e. every
> single byte in each direction). hcidump seems to be a bit too high-level.
> what would you recommend to spy transparently the ttyS0 ?

what kind of Bluetooth chip is it that you use?

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

      reply	other threads:[~2004-02-27 11:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27  8:45 [Bluez-devel] dumping/debuging ttySX Bitterlich Jean-Yves ICM MP PD TI 10
2004-02-27 11:47 ` 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=1077882443.2843.27.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=jean-yves.bitterlich@siemens.com \
    /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