[Maverick] [Pull for ti-omap4]: update to TI July OMAP kernel release L24.8 (try #2)

Tim Gardner tim.gardner at canonical.com
Wed Aug 4 19:05:25 UTC 2010

On 08/03/2010 08:53 PM, Bryan Wu wrote:
> On 08/04/2010 12:53 AM, Tim Gardner wrote:
>> On 07/28/2010 02:04 PM, Tim Gardner wrote:
>>> On 07/28/2010 09:34 AM, Bryan Wu wrote:
>>>> This update includes more than 220 patches which are from TI latest
>>>> July OMAP
>>>> kernel release L24.8. Although it is still based on 2.6.34 kernel, it
>>>> fixed
>>>> lots of bugs, updated syslink driver, imported some ARM common fixes
>>>> and added
>>>> support for new ES2.0 hardware.
>>>> I tested on my OMAP4 based Panda board, it is more stable than before.
>>>> Kernel
>>>> oops about bad_pages was gone. Tried to update to latest Ubuntu
>>>> Maverick and
>>>> didn't see any kernel series oops as before.
>>>> BugLink: http://bugs.launchpad.net/bugs/605739
>>>> I fixed lots of coding sytle issues, but I still keep some warning and
>>>> errors
>>>> there:
>>>> - warning (line over 80 characters): keep them for header files, macros
>>>> - 2 errors ("foo * bar" should be "foo *bar") are checkpatch.pl bug
>>>> - 2 errors: changing file permissions
>>>> - warning (do not add new typedefs): need rewrite too much code
>>>> - warning: using volatile
>>>> These issues need TI guys to fix in the future. I also marked in the
>>>> commits
>>>> after I fixed the coding style.
>>>> The following changes since commit
>>>> bb31cd255b992ee994b6a6aa328acede6460d747:
>>>> Tim Gardner (1):
>>>> UBUNTU: Ubuntu-2.6.34-902.6
>>>> are available in the git repository at:
>>>> git://kernel.ubuntu.com/roc/ubuntu-maverick ti-omap4
>>> NAK - test build FTBS. See attached.
>>> While you're at it:
>>> grep omap log.txt |grep warning
>>> Why are these compiles so noisy? If TI has any hope of upstreaming any
>>> of this code they have to start paying attention to code quality and
>>> style issues.
>>> rtg
>> Bryan - were you able to figure out the build failure?
> Tim,
> In my previous email, I mentioned I've built the kernel successfully. Did you
> get my email?
> We got 5+ more patches now.
> And I still wanna discuss with you guys about the next update of our ti-omap4
> tree. I was told TI will release 2.6.35 based omap4 kernel for us in the middle
> of August. So we will replace the whole ti-omap4 branch shortly, since our
> Maverick kernel target is 2.6.35. How about we skip this 2.6.34 release and just
> wait for next one?
> Thanks,

Well, since we've a bit of time before 2.6.35 arrives, lets fix the 
problems we've got. The first issue is that 
arch/arm/mach-omap2/twl6030_pwm.c is missing which breaks 
arch/arm/mach-omap2/Makefile:obj-$(CONFIG_LEDS_PWM)                 += 

Perhaps you should make sure your tree is really clean, then build under 
an armel schroot using 'debuild -B'.

Tim Gardner tim.gardner at canonical.com

More information about the kernel-team mailing list