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?
Can you please point me to a release where BT and display/hdmi are working for Panda? It's OK if it is ICS.
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.
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_Linar...
What about asking Linaro guys that actually produce this build?
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.
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,