From: Manuel Naranjo <naranjo.manuel@gmail.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] a2dp, sco and kernel version
Date: Tue, 31 Jul 2007 08:19:52 -0300 [thread overview]
Message-ID: <46AF1AD8.2020703@gmail.com> (raw)
In-Reply-To: <1185871920.27218.44.camel@ubuntu.mpl.access-company.com>
Frederic Dalleau escribi=F3:
>> I'm annoyed by this bug. Several people have been reporting it.
>> It looks like they all uses kernel 2.6.21 and higher.
>> =
>
> I just tested 2.6.22-rc7 and it worked ok :(
Maybe it's not a matter of which version of the kernel you use, but also =
in how you have configured it, which modules you have loaded, etc.
I will check your solution and see how it goes-
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-07-31 11:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 23:24 [Bluez-devel] a2dp, sco and kernel version Manuel Naranjo
2007-07-31 0:26 ` Brad Midgley
2007-07-31 0:34 ` Manuel Naranjo
2007-07-31 8:31 ` Frederic Dalleau
2007-07-31 8:52 ` Frederic Dalleau
2007-07-31 11:19 ` Manuel Naranjo [this message]
2007-07-31 16:29 ` Luiz Augusto von Dentz
2007-07-31 18:22 ` Manuel Naranjo
2007-08-01 7:38 ` Frederic Dalleau
2007-08-01 12:44 ` Manuel Naranjo
2007-08-02 3:22 ` Luiz Augusto von Dentz
2007-08-02 4:02 ` Manuel Naranjo
2007-08-02 13:04 ` Frederic Dalleau
2007-08-02 13:05 ` Frederic Dalleau
2007-08-02 15:18 ` Manuel Naranjo
2007-08-02 18:53 ` [Bluez-devel] a2dp, sco and kernel version [Possible Solution] Manuel Naranjo
2007-08-02 19:12 ` Brad Midgley
2007-08-02 19:24 ` Manuel Naranjo
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=46AF1AD8.2020703@gmail.com \
--to=naranjo.manuel@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.