----- "Rene Rebe" <[email protected]> wrote: > Hi all, > > as we got so many newcomers recently, I wanted to share a note how to > use T2 with random embedded boards on platforms that require a custom > kernel for (nearly) each supported board (like ARM, MIPS, SuperH and > such). > > For boards with support already in the vanilla kernel (e.g. > Beagleboard & Co), just copy the Linux example config as custom kernel > config doing so: > > ./scripts/Config -cfg cross-arm # or whatever > > [*] Show expert and experimental options > > ===> Linux Kernel Options > > (none) Do not perform any automatic kernel configuration > > =*= Apply custom kernel build configuration settings > > Copy the linux depconfig from the kernel source: > > cp linux/arch/arm/config/omap3_beagle_defconfig > /config/cross-arm/linux.cfg > > And you get the kernel matching your esoteric board. > > If your board is not support in the vanilla kernel you also have to > hunt (or write) dedicated support and drop the changes as patches into > package/*/linux26/ > > Of course all this is best stored in your dedicated target config > directory in target/.../... > > But I just wanted to share the most straight forward way to build > binaries for some random development board. > > If you also want to build the (re-)boot loader from source, you also > have to hunt the specific u-boot patches respectively, ... >
Thank you Rene! I've been evaluating T2 as a candidate for some embedded systems work and this is one of the things I've been banging my head on. --Tim ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
