From: Marcel Holtmann <marcel@holtmann.org>
To: Philip Blundell <pb@nexus.co.uk>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] lmx9814
Date: Sun, 15 Feb 2004 18:18:19 +0100 [thread overview]
Message-ID: <1076865499.2840.8.camel@pegasus> (raw)
In-Reply-To: <1076864335.23437.70.camel@dixie.nexus.co.uk>
Hi Philip,
> I've been trying to use BlueZ on an HP iPAQ H5500, which uses a National
> LMX9814 chip interfaced via UART. Connecting with "hciattach /dev/tts/1
> any 921600" seems to work ok, and hcitool dev shows the device as hci0,
> but a subsequent hcitool scan fails with "connection timed out". dmesg
> shows:
>
> hci_cmd_task: hci0 command tx timeout
> hci_cmd_task: hci0 command tx timeout
> h4_recv: Unknown HCI packet type 70
> h4_recv: Unknown HCI packet type f8
> h4_recv: Unknown HCI packet type f0
>
> Is anybody successfully using one of these devices, or does anybody have
> a suggestion as to what might be going wrong here?
are you sure that this iPAQ contains a National chip? I thought they are
using a CSR chip and only the never 2xxx series contain a Zeevo chip.
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 prev parent reply other threads:[~2004-02-15 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 16:58 [Bluez-devel] lmx9814 Philip Blundell
2004-02-15 17:18 ` Marcel Holtmann [this message]
2004-02-15 17:21 ` Philip Blundell
2004-02-15 17:29 ` Marcel Holtmann
2004-02-15 18:30 ` Philip Blundell
2004-02-15 18:45 ` 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=1076865499.2840.8.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=pb@nexus.co.uk \
/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