Re: OMAP34xx

[Russell King - ARM Linux <linux@arm.linux.org.uk>]

On Tue, Feb 07, 2012 at 04:08:23PM -0800, Kevin Hilman wrote:
> Víctor M. Jáquez L. <vjaquez@igalia.com> writes:
> > If it helps, I observed the same issue in a beagleboard rev B6, with
> > v3.3-rc2
> 
> Great, thanks.  Can you share your ~/.config?

If it helps, ARM Kautobuild V2 is up and running (assuming I don't break
the scripts again) at:

  http://www.arm.linux.org.uk/developer/build/

from where the build configs I use (and the exact ones used in those
compiles) are available.  These aren't configs in arch/arm/configs.

The OMAP oldconfig builds represent my test configs that I try to boot on
my boards.  This version of Kautobuild not only builds kernels, but it
also packages the built image and modules into a tar file.  Everything
else is discarded.

As of yesterday evening, it also transfers the built image to a TFTP
server ready for boards to fetch for boot testing.

The base kernel which is currently being used for this is whatever state
my working tree is in when it runs, so it's not _that_ useful externally
at the moment.

Currently, the builds run on my working laptop, targetted at 2am each
night local time (though they're a little more sporadic at the moment.)
The downside to them running on the laptop is that when I take the
laptop away, they won't run.


I also have a program which monitors a tty port, detects the initial
booting of a board, and can talk to the boot loader and kernel to instruct
them to do various things (like telling uboot to load one of the tftp'd
kernels.)

However, there's a few bits missing from being able to finish this system
off:

(a) properly detecting on machines monitoring boards when a new kernel is
    ready for testing.
(b) sorting out how to reliably reboot the various boards in a safe manner
(c) working out where and how to connect all these boards in a safe manner

For most boards, switching the mains to their individual power supplies
will work.  For something like the OMAP3430 LDP, it's complicated by its
built-in battery which has to be connected for it to power up at all.
It can't be left plugged in because it drains the battery even with an
external USB charger.

As the OMAP4430 only provides USB, practically it's going to have to be
left out of the automatic stuff because I don't have a machine which it
could be connected to which wouldn't also be part of the boot test farm.

In other words, the OMAP platforms I have will only be manually boot
tested for the forseeable future.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html