mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Christian Kapeler <christian.kapeller@cmotion.eu>
Cc: support@karo-electronics.de, barebox@lists.infradead.org
Subject: Re: [PATCH] Add support for Karo TX51 module
Date: Sun, 18 Mar 2012 16:22:05 +0100	[thread overview]
Message-ID: <20120318152205.GU3852@pengutronix.de> (raw)
In-Reply-To: <4F65C69D.5060500@cmotion.eu>

On Sun, Mar 18, 2012 at 12:27:25PM +0100, Christian Kapeler wrote:
> Hi,
> 
> the attached patches introduce basic barebox support for the Karo
> SO-DIMM TX51 SOC modules.
> Note, that the code is not tested with the Starterkit development
> board as base,
> but on our own custom board.
> 
> Currently the board boots, supports nand, and mmc. Ethernet support
> is currently only working,
> when barebox is chainloaded from Redboot shipped with the modules.

Looks mostly good, except for the FEC debugging of course. One thing
about it is that rather than hand patching the iomux files we should
just update them from the kernel. I have a patch in my queue which
updates basic iomux-v3 support so that just like in the kernel the
iomux pad is not a struct anymore but a 64bit type. This should make
the way free to use the kernel iomux files. Given that your patch
is not yet ready I still have some time to bring this into shape.

Sascha


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

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

      reply	other threads:[~2012-03-18 15:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-18 11:27 Christian Kapeler
2012-03-18 15:22 ` Sascha Hauer [this message]

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=20120318152205.GU3852@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=christian.kapeller@cmotion.eu \
    --cc=support@karo-electronics.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