From: Marko Milutinovic <markomilutin@gmail.com>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: New MACH Addition
Date: Mon, 18 Apr 2011 15:04:52 -0600 [thread overview]
Message-ID: <BANLkTin8CVuTCZTQ=23mw8RpiPV3Lg=8ZQ@mail.gmail.com> (raw)
In-Reply-To: <20110418183847.GO3811@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 2115 bytes --]
Hello,
By kernel do you mean the Linux kernel? I'm just starting work on that, so
not quite sure how that's going to go.
If you mean barebox then yes. I'm using fairly new code, I had to make some
modifications to bypass dealing with cache and MMU as this chip does not
have support for it. The changes were minor.
I will go through my revisions and make sure it conforms to how everything
else is done in this project and see about merging it in.
Thanks,
Marko
On Mon, Apr 18, 2011 at 12:38 PM, Robert Schwebel <r.schwebel@pengutronix.de
> wrote:
> Hi Sascha,
>
> On Mon, Apr 18, 2011 at 08:33:13PM +0200, Sascha Hauer wrote:
> > On Mon, Apr 18, 2011 at 12:17:47PM -0600, Marko Milutinovic wrote:
> > > 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.
>
> We should somewhere have a board with this chip in the archive:
>
> http://www.phytec.de/de/produkte/module-im-ueberblick/phycore/produktdetails/p/phycore-at91m55800a.html
>
> Marko, are you working with a recent mainline kernel on this cpu? I'm
> wondering about the mmu-less state of the kernel. Havn't tried for some
> time.
>
> rsc
> --
> 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 |
>
[-- Attachment #1.2: Type: text/html, Size: 3062 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-04-18 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 18:17 Marko Milutinovic
2011-04-18 18:33 ` Sascha Hauer
2011-04-18 18:38 ` Robert Schwebel
2011-04-18 21:04 ` Marko Milutinovic [this message]
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='BANLkTin8CVuTCZTQ=23mw8RpiPV3Lg=8ZQ@mail.gmail.com' \
--to=markomilutin@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=r.schwebel@pengutronix.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