From: Rogan Dawes <rogan@dawes.za.net>
To: "Eric Bénard" <eric@eukrea.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: Porting to Marvell 88F5182?
Date: Sat, 31 Jul 2010 20:41:03 +0200 [thread overview]
Message-ID: <4C546E3F.4020002@dawes.za.net> (raw)
In-Reply-To: <4C54525F.5030306@eukrea.com>
On 2010/07/31 6:42 PM, Eric Bénard wrote:
> Le 31/07/2010 18:05, Rogan Dawes a écrit :
>>>> But won't the second stage loader simply use the existing memory map? I
>>>> suppose I could tell it what it actually is, if it can't figure it out.
>>>> I'm a little surprised it doesn't "just work", because I am currently
>>>> booting using an old U-boot, chaining to a newly compiled U-Boot,
>>>> and it
>>>> "just works" (apart from the flash).
>>>>
>>> yes but the new u-boot has all the necessary low level access for your
>>> hardware !
>>
>> Well, the new U-Boot also skips the lowlevel init code, so . . .
>>
> what it skips is "only" sdram and pll setup, not serial drivers or timer
> functions.
>
> Eric
Ok, cool. Which is the simplest ARM board for me to use as a template?
I'm not much of a coder, more a "copy and paste monkey", I'm afraid, so
I dunno how well I'll do :-) But I'm willing to give it a shot!
I've looked at the arch/arm/mach-s3c24xx directory, which *seems* to be
the simplest (in terms of fewest files :-) ). Would this be a reasonable
place to start?
Rogan
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-07-31 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 19:50 Rogan Dawes
2010-07-31 11:21 ` Rogan Dawes
2010-07-31 12:36 ` Eric Bénard
2010-07-31 15:20 ` Rogan Dawes
2010-07-31 15:49 ` Eric Bénard
2010-07-31 16:05 ` Rogan Dawes
2010-07-31 16:42 ` Eric Bénard
2010-07-31 18:41 ` Rogan Dawes [this message]
2010-07-31 19:33 ` Eric Bénard
2010-07-31 20:05 ` Rogan Dawes
2010-08-02 5:37 ` Sascha Hauer
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=4C546E3F.4020002@dawes.za.net \
--to=rogan@dawes.za.net \
--cc=barebox@lists.infradead.org \
--cc=eric@eukrea.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox