From: Marcel Holtmann <marcel@holtmann.org>
To: egroJorge <egroJorge@terra.es>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] uclinux and bluez
Date: Sun, 09 May 2004 00:09:34 +0200 [thread overview]
Message-ID: <1084054174.4420.169.camel@pegasus> (raw)
In-Reply-To: <143918984.20040508155253@terra.es>
Hi Jorge,
> I noticed that hciattach doesnt seem to work in uclinux: i could never
> get a "up" device ("hciconfig hci0 up" always failed). In Linux it works
> perfectly. So I compared the behaviour in both system and realised
> that in linux hciattach sends a 0x01x03x10x00 and in uclinux not. I
> think that the sentence "ioctl(fd, HCIUARTSETPROTO, u->proto)" is
> which send that in linux but no in uclinux (although doesnt fail in
> uclinux, simply doesnt send nothing). I was able to see it thanks to a
> oscilloscope.
> I havent study the bluetooth protocols but I tried to send the
> 0x01x03x10x00 "by hand", opening the ttySx in 115200 baudrate and
> writing to it directly (with an auxiliar program I wrote).
what kind of hciattach command do you use? What kind of Bluetooth module
do you use? What endian is your ucLinux platform?
> I know it is not an elegant method and maybe this will only work with
> my hardware configuration. I have no idea of why "ioctl(fd,
> HCIUARTSETPROTO, u->proto)" is not working but I suppossed it was
> fault of the uclinux system (it has a 2.4.20 linux kernel).
This ioctl sets the H4 or BCSP mode of the hci_uart driver.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-05-08 22:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 14:24 [Bluez-devel] Sdp Jorge González
2004-05-06 21:05 ` Marcel Holtmann
2004-05-07 10:20 ` [Bluez-devel] Sdp (and uclinux) Jorge A. González
2004-05-07 16:15 ` Marcel Holtmann
2004-05-08 13:52 ` Re[2]: [Bluez-devel] uclinux and bluez Jorge A. González
2004-05-08 22:09 ` Marcel Holtmann [this message]
2004-05-09 11:35 ` Jorge A. González
2004-05-09 11:42 ` 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=1084054174.4420.169.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=egroJorge@terra.es \
/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