From: Marcel Holtmann <marcel@holtmann.org>
To: Kevin Page <bluez-devel@krp.org.uk>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>,
Russell King <rmk@arm.linux.org.uk>
Subject: Re: [Bluez-devel] re: UART-based bluetooth stuff / serial_cs problems solved?
Date: Wed, 03 Nov 2004 20:12:32 +0100 [thread overview]
Message-ID: <1099509152.7125.155.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.58.0411031821120.19391@moog.ecs.soton.ac.uk>
Hi Kevin,
> > > With linux-2.6.10-rc1-mm2:
> > > hciattach /dev/ttyS3 socket
> > > seems to complete ok (none of the "BCSP initialization timed out"
> >
> > Can you retest it with 2.6.10-rc1-bk13 and see if these patches are
> > already merged back mainline.
>
> Ok, just tested this, and hciattach fails with "BCSP initialization
> timed out", as it does with earlier kernels - so the significant
> modifications must be in the mm2 patches (though I couldn't say
> where!).
too bad, but I think we are on the right way.
Russel, do you may know what patches from -mm are not merged back
mainline at the moment and Kevin can apply one by one to find out what
makes these cards working again?
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&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-11-03 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 11:38 [Bluez-devel] re: UART-based bluetooth stuff / serial_cs problems solved? Kevin Page
2004-11-03 15:41 ` Marcel Holtmann
2004-11-03 18:21 ` Kevin Page
2004-11-03 19:12 ` 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=1099509152.7125.155.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@krp.org.uk \
--cc=bluez-devel@lists.sourceforge.net \
--cc=rmk@arm.linux.org.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