From: Marcel Holtmann <marcel@holtmann.org>
To: Kutschenreuter Matthias <Matthias.Kutschenreuter@siemens.com>
Cc: Stephen Crane <steve.crane@rococosoft.com>,
"'Bluez-devel@lists.sourceforge.net'"
<Bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] pand + socket filtering on zaurus
Date: Thu, 03 Jun 2004 17:32:00 +0200 [thread overview]
Message-ID: <1086276720.7542.180.camel@pegasus> (raw)
In-Reply-To: <AFE91B59A185A5439840B43AB7919047093989@mchp997a.mch.sbs.de>
Hi Matthias,
> OK, I got the ROM 3.10 and installed the latest bluez-2.4.18...ipk
> sucessfully. Then, I do NOT enter a BT CF Card, which I assume would wrok
> perfectly, but I connect a BT Chip using a serial cable instead.
> # modprobe l2cap
> # modprobe hci_uart
> # hciattach /dev/ttyS0 any 115200 flow
> fails ----> "Can't set device: Protocol not support"
> no matter whether I am using the hciattach kindly sended
> by Steve or the one that I cross compiled myself, the answer is always the
> same.
this problem occurs when hciattach will set the device mode (H4 or BCSP)
and I suspect your hci_uart is very old. In the beginning there was no
switch needed, but it also only supported H4. Maybe it is enough to
erase the ioctl(HCIUARTSETPROTO), but using a too old BlueZ stack is not
a good idea.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next parent reply other threads:[~2004-06-03 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AFE91B59A185A5439840B43AB7919047093989@mchp997a.mch.sbs.de>
2004-06-03 15:32 ` Marcel Holtmann [this message]
[not found] <AFE91B59A185A5439840B43AB791904709398A@mchp997a.mch.sbs.de>
2004-06-03 16:16 ` [Bluez-devel] pand + socket filtering on zaurus Marcel Holtmann
2004-06-02 15:51 AW: AW: AW: AW: " Kutschenreuter Matthias
[not found] ` <1086193144.7888.694.camel@baroque.rococosoft.com>
2004-06-03 10:36 ` Marcel Holtmann
[not found] <AFE91B59A185A5439840B43AB7919047093983@mchp997a.mch.sbs.de>
2004-06-01 14:53 ` Marcel Holtmann
[not found] ` <1086101397.2777.597.camel@baroque.rococosoft.com>
2004-06-01 14:56 ` Marcel Holtmann
[not found] <AFE91B59A185A5439840B43AB7919047093974@mchp997a.mch.sbs.de>
2004-05-26 10:00 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2004-05-25 15:31 Kutschenreuter Matthias
2004-05-25 15:48 ` 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=1086276720.7542.180.camel@pegasus \
--to=marcel@holtmann.org \
--cc=Bluez-devel@lists.sourceforge.net \
--cc=Matthias.Kutschenreuter@siemens.com \
--cc=steve.crane@rococosoft.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