Re: [PATCH 1/1] ARM: OMAP4: Add OMAP4 Blaze Tablet support
From: Tony Lindgren
Date: Mon Feb 11 2013 - 11:53:02 EST
* Ruslan Bilovol <ruslan.bilovol@xxxxxx> [130210 13:46]:
> On Sun, Feb 10, 2013 at 4:52 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote:
> > Hi,
> > * Ruslan Bilovol <ruslan.bilovol@xxxxxx> [130208 11:41]:
> >> The OMAP4 Blaze Tablet is TI OMAP4 processor-based
> >> development platform in a tablet formfactor.
> >> The platform contains many of the features found in
> >> present-day handsets (such as audio, video, wireless
> >> functions and user interfaces) and in addition
> >> contains features for software development and test.
> >> This patch adds initial support for the OMAP4 Blaze
> >> Tablet development platform. Additional functionality
> >> depends on different drivers and code modifications that
> >> are not upstreamed yet so will be added later.
> > Nice that you have it working, however, we're not adding
> > any more board-*.c files as we're moving things to device
> > tree based booting.
> Hmm.. I though at this time we require boardfile + DT support..
> Probably lot of boardfiles confused me - any plan to delete them?
> Anyway, the whole era of boardfiles has gone.. (Where to place board-specific
> hacks now? :) )
The DT booting happens with board-generic.c, and we're
should not need board specific callback functions any
longer. That of course assumes we have a Linux generic
framework available for things that we've been doing with
the board specific callback functions.
> > Care to try to get the basic .dts file done for this?
> > You will probably need to add CONFIG_ARM_APPENDED_DTB=y
> > and CONFIG_ARM_ATAG_DTB_COMPAT=y to omap2plus_defconfig
> > and append the .dtb file to zImage and run mkimage then
> > manually to boot it. But you should get serial and MMC
> > at least working to start with :)
> Yes, this is a second part of this board' upstreaming.
> Thanks for advice and please expect DT-part only of board soon..
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/