Fwd: Closed patch not in andy-tracking

[Franky Van Liedekerke]

(sorry, this was supposed to go to the list)

On Tue, Apr 7, 2009 at 12:06 PM, Radek Polak <psonek2 at seznam.cz> wrote:

> Franky Van Liedekerke wrote:
>
>> Hi all,
>>
>> I just saw that the patch mentioned here
>> https://docs.openmoko.org/trac/ticket/1744#comment:7
>> is not in the latest andy-tracking. Is this the intention? It seems
>> bluetooth still experiences the same kind of issues.
>>
>> Franky
>>
>
> Hi Franky,
> which patch do you mean? Because this one:
>
>
> http://git.openmoko.org/?p=kernel.git;a=commit;h=75d17a700b015cd5e99636db035c8bd1324eeca4
>
> is in andy tracking, check this log:
>
>
> http://git.openmoko.org/?p=kernel.git;a=shortlog;h=refs/heads/andy-tracking;pg=1
>
> and search for
>
> "Subject: ohci_s3c2410: Implement PM resume functionality"
>
> Radek
>
>
Hi Radek (nice to see you here as well :-)),

indeed it is in ... weird, I checked and doublechecked and must have missed
this :-)
The thing is that in a 2.6.28 kernel, my bluez needs to be downgraded to
version 3, otherwise qtextended doesn't work (the fso kernel gives me
version 4, but that's not a problem I can't fix). Only after a fresh
restart, I can use bluetooth, not after unsuspend. If I manually restart
bluetooth completely after unsuspend, then the device becomes available
again in qtextended (so easy fix), but still no more pairing is possible. Is
there a commandline way of testing if bluetooth still works ok after
unsuspend?

Franky
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openmoko.org/pipermail/openmoko-kernel/attachments/20090407/b2ea2a9b/attachment.htm