From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHv2 0/6] am33xx: support non-ti boards
Date: Wed, 24 Oct 2012 09:01:36 -0700 [thread overview]
Message-ID: <508810E0.8070704@ti.com> (raw)
In-Reply-To: <87zk3blvxi.fsf@macbook.be.48ers.dk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/24/12 08:41, Peter Korsgaard wrote:
>>>>>> "Peter" == Peter Korsgaard <peter.korsgaard@barco.com>
>>>>>> writes:
>
> Hi,
>
> Peter> The am33xx code currently contains a number of details
> specific Peter> to the ti(-derived) boards in the common code. This
> series Peter> restructures the arch code to make it possible to add
> other Peter> boards.
>
> Peter> This series does not yet any new boards, as the board I'm
> Peter> working on is using nand flash, and omap_gpmc hasn't been
> Peter> updated for bch8 / elm support yet. I've started looking at
> it, Peter> but no code so far.
>
> Peter> Instead it has been tested on Beaglebone.
>
> Hi Tom,
>
> You mentioned on IRC that you were happy with this series, but it
> doesn't seem to be merged yet. Is there anything blocking it? It
> isn't particular complicated, but it is bound to cause conflicts
> with any other am33xx changes, so it would be good to get it
> merged.
Just trying to give a window between posting and merging. I've been
holding at around a week which puts this at tomorrow.
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQIcBAEBAgAGBQJQiBDgAAoJENk4IS6UOR1W7loQAJMs/ejH8J76sagGI7Lc1ogq
ktDu4KkK9hTQCewLBhKn/N3wCwm7E3KgXvLLd1zF31jQTFcMJaHFjZJLO5wXr5Cb
xElPaK9xUDSbAUB0eYPf+mfq+VvplW8fA/adMorjAWCMHfJN8ksaBc248rir1uaD
L47CqBqBYUnkr7ZuUrjmUkalLt0udWaDb9Vr13sNa+FyZMWU+X5jbGSxBbf811WB
flK8VrHQY4eFuDskVUgy6pM+6SX+8hiluF8y6WqfzdN+mtPnAlSMt6PPOZuFhLX8
rplOvBMuobgCjObW+pDsrdJ/yggfgzLF1p6Vy/KRdlv4e+V90jLKfpxsDGpFWRQ4
BZIjLgZl/xv/HjbQY0uyeHV9VGhzgT7ulLFl1wsosSl6GzJNBQDmamLeFFBoTYGg
+vvWLD+1uQ2bL5iJ475K6kmtVLS4tWswPviXT9YI7K692QzbD8NKTzyQ8LmpAhyM
ct1Wat1Nup2fggO14QA4bah1tf37b0MwjYEZfDXszVxR7OjtBa2b3/QdL8uBsCC5
gNrE5/Dpc+3hla71hkOMh7D/UPu0iYbcS3bQsXeTx8zON/1wixY5L53sAOzyL0kp
hkMZh/5ygT1+5SvRB48kUPxxQIIsvybrz3bnRxYzFeDGo6h8HuATMS8XaRhRi9Ui
WoIYL6dl3WlCHXT9GhMh
=KJ4+
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-10-24 16:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 11:21 [U-Boot] [PATCHv2 0/6] am33xx: support non-ti boards Peter Korsgaard
2012-10-18 11:21 ` [U-Boot] [PATCHv2 1/6] am33xx/board.c: make wdtimer/uart_base static Peter Korsgaard
2012-10-18 11:21 ` [U-Boot] [PATCHv2 2/6] am33xx: move ti i2c baseboard header handling to board/ti/am335x/ Peter Korsgaard
2012-10-18 17:12 ` Tom Rini
2012-10-18 18:28 ` Peter Korsgaard
2012-10-18 11:21 ` [U-Boot] [PATCHv2 3/6] am33xx/board: use cpu_mmc_init() for default mmc initialization Peter Korsgaard
2012-10-18 11:21 ` [U-Boot] [PATCHv2 4/6] am33xx: move generic parts of pinmux handling out from board/ti/am335x Peter Korsgaard
2012-10-18 11:21 ` [U-Boot] [PATCHv2 5/6] am33xx: support board specific ddr settings Peter Korsgaard
2012-10-18 11:21 ` [U-Boot] [PATCHv2 6/6] am33xx/ddr_defs.h: rename DDR2/DDR3 defines to their actual part numbers Peter Korsgaard
2012-10-24 15:41 ` [U-Boot] [PATCHv2 0/6] am33xx: support non-ti boards Peter Korsgaard
2012-10-24 16:01 ` Tom Rini [this message]
2012-10-24 19:20 ` Peter Korsgaard
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=508810E0.8070704@ti.com \
--to=trini@ti.com \
--cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.