On 06/23/2011 05:04 PM, Somebody in the thread at some point said:
On 23 June 2011 08:51, Andy Green<andy.gr...@linaro.org> wrote:
Hi -
I mentioned this already to npitre but for various reasons we are planning
to target 3.0 kernel rather than linux-linaro-2.6.39 at the moment. 2.6.39
has some known issues like no onboard audio or HDMI audio, but since 3.0 has
a new and better ALSA implementation for Panda I'm not sure it's worth
spending time on when the old implementation won't really go into
linux-linaro even if we did forward-port it again.
What does this mean for the 11.06 OMAP Android release? Will it
use your 3.0 kernel or will it use 2.6.35 again?
I'm not certain what the android folks are doing but I have also tagged
"android-2.6.38-2011-06" on my repo which is a 2.6.38 branch that boots
into Android fine with 3D acceleration, just with 640 x 480 raster and
framebuffer. I know Zach is familiar with this and has been preparing
the way, so I think we might see that one go out this month.
I introduced two new branches yesterday:
http://git.linaro.org/gitweb?p=people/andygreen/kernel-tilt.git;a=shortlog;h=refs/heads/tilt-tracking
- omap4_defconfig
http://git.linaro.org/gitweb?p=people/andygreen/kernel-tilt.git;a=shortlog;h=refs/heads/tilt-tracking-android
- android_omap4_defconfig
that are linus' HEAD and common-3.0 (androidized nearly linus HEAD) based
and have the API v4403 SGX stuff on them.
How hard is it to just grab the OMAP-specific patches from
3.0-rc<latest>and move them to 2.6.39?
Well, the point is linux-linaro-* would be a common place that all the
LT kernels can contribute to.
For example if this new 4430 Alsa implementation has dependencies on
Alsa core stuff only in 3.0, we're back in the same bind as the
forwardport of the 2.6.38 Alsa driver which has "special needs" in Alsa
core stuff that conflicts with other LEB audio driver assumptions.
In the end demand downstream of us is only for 3.0, they won't get any
direct benefit from time spent servicing 2.6.39.
The status is currently on linus HEAD, Panda EHCI is broken which is a bit
of a downer; Jassi is taking a look at it. Also video is coming up nicely
with 1080p raster, but it is stuck at 640 x 480 framebuffer viewport inside
that right now.
Is this something that upstream is also aware of and tracking?
What the EHCI debug effort you mean? There's no fruit from it yet but
sure, since we happen to be riding Linus HEAD if we find something
applicable to upstream I don't doubt Jassi will send it there straight away.
-Andy
--
Andy Green | TI Landing Team Leader
Linaro.org │ Open source software for ARM SoCs | Follow Linaro
http://facebook.com/pages/Linaro/155974581091106 -
http://twitter.com/#!/linaroorg - http://linaro.org/linaro-blog
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
