Hi,


On 18 August 2013 12:25, Andy Green <andy.green@linaro.org> wrote:
On 18 August 2013 14:41, Fathi Boudra <fathi.boudra@linaro.org> wrote:
> Hey Mike,
>
> On 17 August 2013 20:07, Mike Turquette <mturquette@linaro.org> wrote:
>> On Thu, Aug 15, 2013 at 6:02 PM, Andy Green <andy.green@linaro.org> wrote:
>>> On 16 August 2013 08:22, Mike Turquette <mturquette@linaro.org> wrote:
>>>> Hi all,
>>>>
>>>> I'm interested in looking at some Bluetooth stuff on my OMAP 4460
>>>> Panda ES. Looking at the bug reports I don't see any Jelly Bean
>>>> releases that have BT working properly on Panda. Is this correct?
Yes. This is true. We have not worked on fixing BT on JB.
>>>>
>>>> Can you please point me to a release where BT and display/hdmi are
>>>> working for Panda? It's OK if it is ICS.
 Even on ICS it was partially working. File transfer resulted in crashes on 4.0.4. You can try this release which is based on 4.0.3 :
http://releases.linaro.org/12.03/android/leb-panda/

It was working well on GB if you are interested:

>>>>
>>>> I'm OK starting with binaries but I would much prefer to be able to
>>>> build from source and reproduce any known-good bins. I have already
>>>> built JB from the latest tip as well as the 13.07 manifest (display is
>>>> working fine but BT doesn't work, bugs already filed). I tried the
>>>> 12.07 Panda LEB (which I think was the last ICS release?) but the
>>>> binaries supplied did not have display working even after running the
>>>> install-binaries-4.0.4.sh script.
12.07 did not need any acceleration binaries since it was based on 3.4 kernel where SGX was not ported back then. Since we were not making any progress with 3.4 kernel, we moved back to 3.2 kernel.
>>>
>>> Nicolas Dechesne may be able to help more directly, but mainline BT
>>> was never workable reliably on Panda.
>>
>> That's disappointing since an article on omappedia references the
>> Linaro release and says, "Note: Wifi, bluetooth, YouTube, jpeg, video
>> playback (both .mp4 and .3gp), and audio playback (both .mp3 and .aac)
>> all have been verified as working in this release." You can see it
>> here:
>>
>> http://www.omappedia.com/wiki/Android_Panda_Build_Source#Building_from_Linaro
>
> What about asking Linaro guys that actually produce this build?
I am trying to get this build working again:
https://android-build.linaro.org/builds/~linaro-android-archive/panda-ics-gcc47-omapzoom-stable-blob/

This build is based on 3.0 kernel which had most of the connectivity working and included MM support as well. I'll get back to you once the build is succesful again.
>
> Looking at our test results, the bluetooth test failed in 12.07 release.
> A bug has been opened at that time:
> https://bugs.launchpad.net/linaro-android/+bug/987765
>
> Adding Vishal in CC, who's probably know the bluetooth status in
> Linaro Android builds better than me.

Mike's saying even video didn't work when he tried that.

Reading that bug it sounds like a firmware issue in the image.  I say
in the bug it's working on kernel side at that time.

However like the video problem, it sort of hinges on the meaning of "working".

HDMI and DVI on Panda have "worked" to some extent for a long while.
But they've never worked properly dual-head and in fact because they
share a PLL for the pixel clock, they'll never work outside of special
conditions like same monitor and resolution.  Last I saw of it there's
a behaviour in HDMI hotlug detect handling in the driver that means
some monitors won't be seen as plugged, because they delay sending hpd
by up to 1s (I have one of these monitors).  The code in the Panda
release was forward-ported from 3.0 DSS stack on omapzoom (since
that's the only thing TI had on offer with working Android SGX) and
that deviates hugely from mainline DSS, so any improvements in this
area didn't get transplanted.

Bluetooth is similar on mainline basis, it was able to work for a
while but when hammered it fell over.

-Andy

>>> The p-android stuff on omapzoom was meant to have numerous patches
>>> that actually made it work.  At one point we talked to some guys from
>>> TI and got some patches, however they were patches against
>>> p-android-3.0 that not only did not apply on mainline but were 100%
>>> patching code that anyway did not exist in mainline, so we got
>>> literally nowhere with it.
>>>
>>> The p-android stuff are busy history trees, so it is very hard to
>>> extract a coherent series that "fixes bluetooth".  Even to do direct
>>> diffs at file level isn't easy since the files have all moved around
>>> and the 3.0 one we know worked is radically different than current
>>> mainline anyway.  Some of the issues were down to PM related stuff and
>>> the p-android arrangements for that bear no relationship to mainline.
>>>
>>> Anyway Nicolas may know more, but the best bet may be to find a TI
>>> Alumni who worked on it and get the skinny.
>>
>> Nicolas, any inputs?
>>
>> Thanks,
>> Mike
>>
>>>
>>> -Andy
>>>
>>>> Thanks,
>>>> Mike
>
> Cheers,
> --
> Fathi Boudra
> Builds and Baselines Manager | Release Manager
> Linaro.org | Open source software for ARM SoCs
>
> _______________________________________________
> linaro-dev mailing list
> linaro-dev@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-dev

_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev