Re: [Bluez-devel] a2dp, sco and kernel version [Possible Solution]

["Brad Midgley" <bmidgley@gmail.com>]

Manuel

On 8/2/07, Manuel Naranjo <naranjo.manuel@gmail.com> wrote:
> I finally could narrow the problem CONFIG_HIGH_RES_TIMERS is the one
> that makes a2dpd fail in certain circumstances. I'm not sure if my
> hardware has support for this feature or not, but anyway it's good to
> know what's causing the problem.
> So to all those of you that have a kernel >= 2.6.21 and can't use a2dpd
> can disable CONFIG_HIGH_RES_TIMERS, recompile and reinstall your
> kernels, and should get a2dpd working again.

the use of highres timers is chosen dynamically at boot based on the
hardware capabilities. There should be a boot parameter to disable it.
That would be helpful for our troubleshooting documentation.

didn't someone say things worked in 2.6.23-rc1 or was that test done
without high-res timers enabled?

brad

-------------------------------------------------------------------------
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