From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: mach header files
Date: Fri, 04 Apr 2014 20:49:58 +0200 [thread overview]
Message-ID: <5208350.A2oo5ltmuY@wuerfel> (raw)
In-Reply-To: <533EF387.9080702@borg.org>
On Friday 04 April 2014 14:01:43 Kent Borg wrote:
> On 04/04/2014 09:24 AM, Arnd Bergmann wrote:
> > Basically at this point we expect zero code in arch/arm/mach-* for a
> > new platform.
>
> I am in a position similar to Phil's, bringing up Linux on emulated
> hardware. And obviously I look at existing code to see how things are done.
>
> What is the cleanest look-here-first, least mach-code, SMP example for
> me to try to slavishly copy?
The trouble with examples here is that the good ones are those
without any code, which is harder to copy than the bad ones ;-)
mach-sunxi is a rather good example, since it was added only
recently. Note that the platsmp.c code in there is only used
for the sun6i variant, which doesn't have a boot loader
implementing the PSCI SMP code yet. IIRC sun7i does this right,
so the .smp pointer is empty.
Most of the code in mach-sunxi is actually just the system-restart
implementation, and my feeling is that this should just be moved
into the watchdog timer driver (there is still some discussion
about that).
Once these things are both done, you can boot a sunxi machine
without any code in mach-sunxi.
An ideal example is mach-moxart, which has zero code.
Can you say what platform you are working on? If I can see
your code, that would make it easier to give you advice.
Arnd
next prev parent reply other threads:[~2014-04-04 18:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 8:19 mach header files Phil Edworthy
2014-04-04 10:29 ` Grant Likely
2014-04-04 12:16 ` Phil Edworthy
2014-04-04 12:22 ` Grant Likely
2014-04-04 13:14 ` Phil Edworthy
2014-04-04 13:20 ` Thomas Petazzoni
2014-04-08 14:00 ` Laurent Pinchart
2014-04-04 13:44 ` Grant Likely
2014-04-04 13:24 ` Arnd Bergmann
2014-04-04 13:32 ` Barry Song
2014-04-04 15:27 ` Arnd Bergmann
2014-04-04 13:52 ` Phil Edworthy
2014-04-04 15:30 ` Arnd Bergmann
2014-04-04 15:42 ` Phil Edworthy
2014-04-04 15:50 ` Arnd Bergmann
2014-04-04 16:02 ` Phil Edworthy
2014-04-04 16:22 ` Russell King - ARM Linux
2014-04-04 16:38 ` Phil Edworthy
2014-04-04 18:01 ` Kent Borg
2014-04-04 18:49 ` Arnd Bergmann [this message]
2014-04-04 19:01 ` Kent Borg
2014-04-04 19:19 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2014-04-02 15:11 Phil Edworthy
2014-04-02 15:16 ` Arnd Bergmann
2014-04-03 7:48 ` Phil Edworthy
2014-04-02 15:20 ` Ben Dooks
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=5208350.A2oo5ltmuY@wuerfel \
--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