From: Sascha Hauer <s.hauer@pengutronix.de>
To: Marko Milutinovic <markomilutin@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: New MACH Addition
Date: Mon, 18 Apr 2011 20:33:13 +0200 [thread overview]
Message-ID: <20110418183313.GP14770@pengutronix.de> (raw)
In-Reply-To: <BANLkTi=FxqCsR1vY_p_i-XVB8g-niciODA@mail.gmail.com>
Hi Marko,
On Mon, Apr 18, 2011 at 12:17:47PM -0600, Marko Milutinovic wrote:
> Hello,
>
> I recently ported barebox to a platform using an old AT91 chip (at91m55800a,
> ARM7TDMI core). There is already a MACH_AT91 folder but this chip is
> sufficiently different that I just made a new folder MACH_AT91_legacy. This
> was just a test project for me to get familiar with using barebox.
>
> I'm just wondering if there is any value in me merging in the code for this?
> I realize it's a pretty old chipset, but I'm finding barebox very useful and
> would like to contribute to it.
I never even heard of this chip. I think adding support for it should be
ok, but we might remove it in the future should non trivial architecture
changes become necessary and nobody cares for updating this.
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
next prev parent reply other threads:[~2011-04-18 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 18:17 New MACH Addition Marko Milutinovic
2011-04-18 18:33 ` Sascha Hauer [this message]
2011-04-18 18:38 ` Robert Schwebel
2011-04-18 21:04 ` Marko Milutinovic
2011-04-19 6:51 ` Robert Schwebel
2011-04-19 15:06 ` Jean-Christophe PLAGNIOL-VILLARD
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=20110418183313.GP14770@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=markomilutin@gmail.com \
/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.