Porting BareBox to Variscite iMX6 SOM
s.hauer at pengutronix.de
Thu Aug 22 17:09:08 EDT 2013
On Thu, Aug 22, 2013 at 03:18:13PM -0400, Michael Burkey wrote:
> Based on a fairly thorough perusal of the current HEAD from the git, I
> am thinking I will implement the Variscite SOM in the following file
> (FYI - the Variscite development kit includes their own carrier board
> which is simply referred to in their published schematics as
> "MX6CustomBoard", so I am thinking of segmenting things by SOM and
> carrier board, much as you have the PhyFlex and its carrier board.)
> /arch/arm/boards/variscite-mx6-custom/env/(To Be Determined)
> Does this fit into your current methodology pretty well?
Yes, this looks good.
Note that i.MX6 boards often come in different quad/dual variants with
slightly different devicetrees. Just to explain the mess we have with
the i.MX6 devicetrees...
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
More information about the barebox