From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] About new hardware testing
Date: Mon, 21 Feb 2005 23:58:09 +0100 [thread overview]
Message-ID: <1109026689.7626.17.camel@pegasus> (raw)
In-Reply-To: <1ffb4b0705022008331572db81@mail.gmail.com>
Hi Mike,
> > I remember we initialy had a problem to get the right default pass for
> > hcid.conf when cross compiling.
> I will try this
> > Does "hciconfig hci0 up" work ??
> Because i do not get any info from hciconfig. I can not "up" the device.
> >
> > I use
> > hciattach /dev/ttyS1 -s 115200 csr 921600 flow
> > to attach the bluetooth device (CSR with HCI connected to an ARM).
>
> My script is like that hciattach /dev/ttyS1 -s 921600 csr 921600
> flow. But it works on my development board, so i don't think it is the
> problem.
I think you should add a lot of printf to the hciattach to see where it
fails. If the hci0 device is not created (hciconfig shows nothing) then
the line discipline of ttyS1 is never changed to HCI.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-02-21 22:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 15:34 [Bluez-devel] About new hardware testing Mike Lee
2005-02-20 15:39 ` Peter Wippich
2005-02-20 15:51 ` Mike Lee
2005-02-20 16:04 ` Peter Wippich
2005-02-20 16:33 ` Mike Lee
2005-02-21 22:58 ` 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=1109026689.7626.17.camel@pegasus \
--to=marcel@holtmann.org \
--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