public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: A good sub-architecture to base new ports on?
Date: Wed, 16 May 2012 15:57:44 +0000	[thread overview]
Message-ID: <201205161557.45362.arnd@arndb.de> (raw)
In-Reply-To: <CAB9v_DFdTkAFQWFthLncx5frJX0jed11CUoKXJDT-ac6j3hWOQ@mail.gmail.com>

On Wednesday 16 May 2012, Alexey Zaytsev wrote:
> Hey.
> 
> With all the ARM tree rework, I'm wondering, what would be a good (and
> simple) sub-architecture on which to base new ports. The target is a
> somewhat dated chip used in ADSL routers, so no DT, or multiplatform.
> I'm looking at ixp4xx, because I'm somewhat familiar with the
> platform, but is it a good reference?

For a new subarchitecture, using DT is required, but it should not make
your work harder. spear3xx/6xx is a good example of an older platform
that was recently converted (take the arm-soc tree as a base, it contains
the latest version).

Another good one would be highbank, but that contains a lot of stuff you
don't need.

ixp4xx is not very actively maintained, so I would not use that as
a base.

What platform are you talking about? I know of a few people that are
working on getting older platforms ported to Linux, so maybe someone
is already working on a port.

	Arnd

  reply	other threads:[~2012-05-16 15:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 13:16 A good sub-architecture to base new ports on? Alexey Zaytsev
2012-05-16 15:57 ` Arnd Bergmann [this message]
2012-05-17 15:29   ` Alexey Zaytsev
2012-05-17 17:24     ` Jorge Amorós Argos
2012-05-18 13:31       ` Arnd Bergmann
2012-05-21 20:19         ` Alexey Zaytsev
2012-05-23 20:41           ` Jorge Amorós Argos
2012-05-28  8:49             ` Volkan K.
2012-05-17 21:04     ` Arnd Bergmann
  -- strict thread matches above, loose matches on Subject: below --
2012-05-27 14:08 Volkan K.

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=201205161557.45362.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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