From: Marcel Holtmann <marcel@holtmann.org>
To: John McCorquodale <mcq@cacr.caltech.edu>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] BCSP initialization timed out
Date: Fri, 16 Jul 2004 08:43:09 +0200 [thread overview]
Message-ID: <1089960189.4517.60.camel@pegasus> (raw)
In-Reply-To: <20040716051048.GA31365@viz.cacr.caltech.edu>
Hi John,
> FAQ: "BCSP initialization timed out" with 2.6 serial_cs
>
> As I understand it, the bluez opinion on this problem is "something changed
> with the serial driver from 2.4 to 2.6, and it's broken now and the problem
> isn't our fault so we're not going to think about it"
>
> I anticipate, if I try to go to kernel types and say this, that their response
> will be something to the effet of "every other serial device works fine in
> 2.6, bluez is broken and the problem isn't our fault so we're not going to
> think about it"
>
> In an attempt to avoid this impasse, could those of y'all who know this
> hardware pause for a moment and try to imagine what might be weird about
> the Uarts in question, and maybe offer some constructive shots in the dark
> about what might make a Socket Communications bluetooth CF card different
> than a normal 16550?
>
> A quick run of od -x shows that the device really does deliver different
> data in 2.4 and 2.6 -- the 2.6 version never sends the 0xc0 that hciattach
> seems to be waiting for, so there really is something different going on
> but I'm trying to avoid a complete shot in the dark and wholesale reading
> of the whole serial implementations in both kernel verions, which is
> tantamount in time and complexity to just rewriting the thing anyway.
even if some people think that I own every Bluetooth device on the
planet that is not true. And actually the cards from Socket and
Brainboxes are these that I don't own. So I've never done any test with
these cards and maybe they started to work with 2.6.8-rc1 or so, because
there are fixes in the serial subsystem.
> Alternatively, if somebody could just recommend a CF card that works in
> 2.6, I'll pitch this one in the trash and get on with life.
I own an old Com1 card that is working in BCSP mode with the serial_cs
driver, but it only works at 115200 baud.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-07-16 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 5:10 [Bluez-devel] BCSP initialization timed out John McCorquodale
2004-07-16 6:43 ` 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=1089960189.4517.60.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=mcq@cacr.caltech.edu \
/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