public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Adding new architecture (nds32) support to u-boot
Date: Fri, 23 Apr 2010 14:19:28 +0200	[thread overview]
Message-ID: <201004231419.28708.marek.vasut@gmail.com> (raw)
In-Reply-To: <50FD90C65C53FB45BADEEBCD84FF07F2023A3DB4@ATCPCS06.andestech.com>

Dne P? 23. dubna 2010 05:42:13 macpaul at andestech.com napsal(a):
> Hi Wolfgang,
> 
> 
> 
> I?m working for Andestech, which is a RISC IP (NDS32) company in Taiwan.
> 
> This company has been started for 5 years.
> 
> In recent , we are planning to release source code such as Linux Kernel and
> GNU toolchain back to communities.
> 
> We also plan to commit code to u-boot.
> 
> 
> 
> I?ve read some materials on u-boot wiki.
> 
> It seems other architectures will maintain their own u-boot git, and you
> will merge their code into your mainline trunk.
> 
> If we want to init a new u-boot git repository for our architecture, should
> we just follow the instructions wrote in
> http://www.denx.de/wiki/U-Boot/CustodianGitTrees ??

Should be OK.
> 
> Since our toolchain haven?t been commit to GNU, could we commit code to
> u-boot before GNU accept our toolchain support?
> 
> Is there anything special that we must provide to you?
> 
> 
> 
> Thanks for your replying.
> 
> 
> 
> Best regards,
> 
> Macpaul Lin
> Mobile: +886-919380156
> 
> Software Engineer
> (Andes Tech.)
> 
> 
> 2F, No.1, Li-Hsin First Road, Science-Based Industrial Park,
> Hsinchu 300, Taiwan, R.O.C.
> Tel: +886-3-6668300 #379
> Fax: +886-3-6668322

  reply	other threads:[~2010-04-23 12:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23  3:42 [U-Boot] Adding new architecture (nds32) support to u-boot macpaul at andestech.com
2010-04-23 12:19 ` Marek Vasut [this message]
2010-04-23 15:05 ` Mike Frysinger

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=201004231419.28708.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.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