From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] RFC: split ARM repo and distribute workload
Date: Sun, 06 Sep 2009 08:54:55 -0500 [thread overview]
Message-ID: <4AA3BF2F.3080703@windriver.com> (raw)
In-Reply-To: <0554BEF07D437848AF01B9C9B5F0BC5D91E07BDA@dlee01.ent.ti.com>
Paulraj, Sandeep wrote:
> Wolfgang, Dirk,
>
> I can take responsibility for TI DaVinci SOCs.
>
>
This means an omap/davinci split ?
u-boot-arm-omap
u-boot-arm-davinci
This is ok with me
Tom
> Thanks,
> Sandeep
> ________________________________________
> From: u-boot-bounces at lists.denx.de [u-boot-bounces at lists.denx.de] On Behalf Of Dirk Behme [dirk.behme at googlemail.com]
> Sent: Saturday, September 05, 2009 3:39 AM
> To: Wolfgang Denk
> Cc: Tom Rix; Kyungmin Park; u-boot at lists.denx.de; Magnus Lilja; Minkyu Kang
> Subject: Re: [U-Boot] RFC: split ARM repo and distribute workload
>
> Dear Wolfgang,
>
> Wolfgang Denk wrote:
>
>> Texas Instruments (OMAP): Dirk Behme?
>> Or are there any volunteers at TI?
>>
>
> I really like to see someone from TI here, instead.
>
> Looking at some past discussions, I think somebody from TI would be
> the best. E.g.:
>
> - While discussing the board/vendor directory change, we were unsure
> who might be the vendor of which board. Somebody from TI would know best.
>
> - While discussing the OMAP3 cache move, we were unsure what's about
> the ROM code calling and where/when this is necessary. Someone from TI
> would know best, too.
>
> - etc, etc.
>
> Best regards
>
> Dirk
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
>
next prev parent reply other threads:[~2009-09-06 13:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 21:57 [U-Boot] RFC: split ARM repo and distribute workload Wolfgang Denk
2009-09-04 23:17 ` Jean-Christophe PLAGNIOL-VILLARD
2009-09-07 6:31 ` Prafulla Wadaskar
2009-09-05 7:39 ` Dirk Behme
2009-09-06 12:41 ` Paulraj, Sandeep
2009-09-06 13:54 ` Tom [this message]
2009-09-06 14:45 ` Paulraj, Sandeep
2009-09-06 15:38 ` Tom
2009-09-06 21:12 ` Wolfgang Denk
2009-09-06 21:25 ` Wolfgang Denk
2009-09-07 1:06 ` Kyungmin Park
2009-09-07 3:02 ` Prafulla Wadaskar
2009-09-07 11:03 ` Wolfgang Denk
2009-09-07 12:51 ` Wolfgang Denk
2009-09-07 14:05 ` Minkyu Kang
2009-09-07 9:06 ` Magnus Lilja
2009-09-07 10:22 ` Wolfgang Denk
2009-09-08 12:45 ` [U-Boot] Merging u-boot-s3c24xx with u-boot-samsung Wolfgang Denk
2009-09-09 11:06 ` Harald Welte
2009-09-21 11:37 ` [U-Boot] RFC: split ARM repo and distribute workload Jean-Christophe PLAGNIOL-VILLARD
2009-09-21 12:44 ` Wolfgang Denk
2009-09-21 16:43 ` Prafulla Wadaskar
2009-09-21 17:48 ` Wolfgang Denk
2009-09-21 17:51 ` Tom
2009-09-21 17:45 ` Tom
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=4AA3BF2F.3080703@windriver.com \
--to=tom.rix@windriver.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