mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Michael Burkey <mdburkey@gmail.com>
To: barebox@lists.infradead.org
Subject: Porting BareBox to Variscite iMX6 SOM
Date: Wed, 21 Aug 2013 14:46:17 -0400	[thread overview]
Message-ID: <CAJyuEedsHb0h84AKDq_Mttxu_ZG1u+gG94BpzioHyO=JdHiD=A@mail.gmail.com> (raw)

Sascha,

You can ignore part of my last post -- I found the
"imx6q-phytec-pbab01" on github (it looks like a lot of the things I
am needing and working on are right on the edge of development where
you are working as well).

I also noticed some posts in the mailing list that you made last month
regarding adding gpmi-nand support for iMX6 (or at least some wrappers
for it). Has the actual gpmi-nand support been completed and
integrated (or will the existing mxs-nand driver from the i.MX23/28
work as-is)?


I've also been doing a lot of reading on devicetree and what it
entails to migrate in that direction (everything I had been doing
previously had been iMX35 based and started from the older Phytec
BSP's, so I hadn't really looked at how devicetree worked). I may have
some more questions on this going forward.

Thanks again,
Michael Burkey

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

             reply	other threads:[~2013-08-21 18:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-21 18:46 Michael Burkey [this message]
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
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='CAJyuEedsHb0h84AKDq_Mttxu_ZG1u+gG94BpzioHyO=JdHiD=A@mail.gmail.com' \
    --to=mdburkey@gmail.com \
    --cc=barebox@lists.infradead.org \
    /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