mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Michael Burkey <mdburkey@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Porting BareBox to Variscite iMX6 SOM
Date: Thu, 22 Aug 2013 15:18:13 -0400	[thread overview]
Message-ID: <CAJyuEedyP-VXLieP5hZgTv5Tiihq9h8fecEpuGV4YdYur=Kq8g@mail.gmail.com> (raw)
In-Reply-To: <20130822065552.GU31036@pengutronix.de>

Sascha,

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
structure:

(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/configs/variscite_mx6_custom_defconfig
/arch/arm/boards/variscite-mx6-custom/board.c
/arch/arm/boards/variscite-mx6-custom/flash-header.imxcfg
/arch/arm/boards/variscite-mx6-custom/lowlevel.c
/arch/arm/boards/variscite-mx6-custom/Makefile
/arch/arm/boards/variscite-mx6-custom/env/(To Be Determined)
/arch/arm/dts/imx6q-var-custom.dts
/arch/arm/dts/imx6q-var-som.dtsi

Does this fit into your current methodology pretty well?

Thanks!
Michael Burkey

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2013-08-22 19:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-21 18:46 Michael Burkey
2013-08-22  6:55 ` Sascha Hauer
2013-08-22 15:49   ` Michael Burkey
2013-08-22 21:06     ` Sascha Hauer
2013-08-22 19:18   ` Michael Burkey [this message]
2013-08-22 21:09     ` Sascha Hauer
  -- strict thread matches above, loose matches on Subject: below --
2013-08-21 15:48 Michael Burkey
2013-08-20 18:12 Michael Burkey
2013-08-21  8:28 ` Sascha Hauer
2013-08-15 18:58 Michael Burkey
2013-08-16  9:47 ` Sascha Hauer
2013-08-16 11:37   ` Alexander Aring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJyuEedyP-VXLieP5hZgTv5Tiihq9h8fecEpuGV4YdYur=Kq8g@mail.gmail.com' \
    --to=mdburkey@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox