From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Re: BT3C_CS broken in kernel 2.6.14? [Also with 2.6.15]
Date: Wed, 04 Jan 2006 12:43:15 +0100 [thread overview]
Message-ID: <1136374995.13931.21.camel@localhost> (raw)
In-Reply-To: <loom.20060104T122021-876@post.gmane.org>
Hi Antti,
> > remember what the real problem or even the solution was when it came up
> > on LKML. Try to do some research on LKML by yourself and also check the
> > latest 2.6.14-git10 kernel.
>
> I tried now with 2.6.15 - Still not fixed. Can you point me to these LKML
> postings? I couldn't find then (tried searching with keywords bt3c, bluetooth
> and firmware - the latter two were too broad and the first did not give
> anything useful.)
it must have been something with the atmel_cs and request_firmware(),
because the atmel_cs and bt3c_cs drivers had the same problem.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-01-04 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 11:29 [Bluez-users] BT3C_CS broken in kernel 2.6.14? Antti Mäkelä
2005-11-07 13:43 ` Marcel Holtmann
2006-01-04 11:22 ` [Bluez-users] Re: BT3C_CS broken in kernel 2.6.14? [Also with 2.6.15] Antti Mäkelä
2006-01-04 11:43 ` Marcel Holtmann [this message]
2006-01-04 11:57 ` Marcel Holtmann
2006-01-04 13:09 ` Antti Mäkelä
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=1136374995.13931.21.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-users@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;
as well as URLs for NNTP newsgroup(s).