From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/5] am33xx: move ti i2c baseboard header handling to board/ti/am335x/evm.{c, h}
Date: Wed, 17 Oct 2012 08:55:32 -0700 [thread overview]
Message-ID: <507ED4F4.4080106@ti.com> (raw)
In-Reply-To: <87vce9qexc.fsf@macbook.be.48ers.dk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/17/12 08:46, Peter Korsgaard wrote:
>>>>>> "Tom" == Tom Rini <trini@ti.com> writes:
>
>
> Tom> I'd like to see it as board/ti/am33xx/board.[ch] but other
> than that I Tom> can see where you're coming from.
>
> Ok, fine - Will use board.{c,h} in next version.
>
> Tom> Can you post a WIP version of your s_init / board_init? I'd
> like Tom> to see what maybe we should call __weak or try and
> restructure a Tom> bit more. Thanks!
>
> Sorry, I only just started the mainline porting work last Friday
> next to other tasks, so right now it basically looks like the ti
> ones except for the eeprom handling, but I'll need to add fpga
> configuration handling and a redundant boot setup using the
> watchdog (E.G. fallback to backup u-boot/linux/rootfs if the system
> didn't start before watchdog fired).
Sounds good.
> Again, I haven't been able to do any real tests on this board
> because of missing nand support. Are you aware of any in progress
> effort on this within TI?
Yes, Ilya Yanok is working on that, as well as finishing MUSB support
currently.
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQIcBAEBAgAGBQJQftT0AAoJENk4IS6UOR1WcU4QAIiIrVc4kAfIucvXSbIjhLXp
aXNvDM3ulopIm6jRW5rXkcSpRrkCRVpOC4waqncR3Wj4RS7AMdPqE4VBmBHtLhLK
hcoSkn5G2VFVmAArsNrnp070OqlGWApyfaM47TEkNdV93ah/ZXpuyd2y+AUFpOoC
uTgU4Y0DWgDQx2+PBGPTzCVo5TVdEtGEnkYWcTtnOOx7dB+QumF2Vy/HDPmUFnmo
BYD+D9t5XX1xOUL9aiKGCthuwa+F22/CNUwOjRkS1h4LnoGBHC8Zy+kEMs+uvXR/
Mn8t5GFL8zi3wh7sOw0MvcyoLrcdV/9OOf32uVobL9IXMIFVUjv+7YXrlxLYUmmN
M9flwEddKnzs92a7KGAY9LZPL/4nqZqqGHRyMewDlJaRMGMrgudI50NxKP5yHdP1
O/m9W4COk9GLw4Cwg3o0/ATjwjT6MvKziV74yih24Qjh5Ti08e5c9fDBeoFnUBsF
PwnSZRcyFkThJBJxJ6jFdb/mbMNNG0Fm/a0IYn1WQk2misOwKfDzVIBdYI4Ej+BP
IAuEXppsNOS1lO4L8JEG/PNo8g8XxJb+TjK5qowGCXrdNIJpB2X/k6vf1ayAZgat
Gu7YYoU+XzzFe4VPK4RCV9ppj7fpd+Jf42+FMOCyjuzc38sprWienBhPJ9JCfN9e
1BK0VkitJBLWhwjtlThH
=7CTb
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-10-17 15:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 15:15 [U-Boot] [PATCH 0/5] am33xx: support non-ti boards Peter Korsgaard
2012-10-16 15:15 ` [U-Boot] [PATCH 1/5] am33xx: move ti i2c baseboard header handling to board/ti/am335x/evm.{c, h} Peter Korsgaard
2012-10-16 15:35 ` Tom Rini
2012-10-17 15:46 ` Peter Korsgaard
2012-10-17 15:55 ` Tom Rini [this message]
2012-10-17 19:24 ` Peter Korsgaard
2012-10-16 15:15 ` [U-Boot] [PATCH 2/5] am335x/evm.c: don't make wdtimer/uart_base global Peter Korsgaard
2012-10-16 15:15 ` [U-Boot] [PATCH 3/5] am33xx/board: use cpu_mmc_init() for default mmc initialization Peter Korsgaard
2012-10-16 15:36 ` Tom Rini
2012-10-16 17:37 ` Peter Korsgaard
2012-10-16 15:15 ` [U-Boot] [PATCH 4/5] am33xx: move generic parts of pinmux handling out from board/ti/am335x Peter Korsgaard
2012-10-16 15:15 ` [U-Boot] [PATCH 5/5] am33xx: support board specific ddr settings Peter Korsgaard
2012-10-16 15:31 ` Tom Rini
2012-10-16 17:43 ` Peter Korsgaard
2012-10-16 21:13 ` Tom Rini
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=507ED4F4.4080106@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox