mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] AT91SAM9263-ek
Date: Thu, 28 Jun 2012 09:52:46 +0200	[thread overview]
Message-ID: <b82fd62bb0ecc8daaf9891b2aede8a80@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <4FEBFCD7.7060607@web.de>

Hei hei,

Am 2012-06-28 08:42, schrieb Stutz Sven:
> Further more to boot this image on the hardware, do I really have to
> use at91bootstrap to load barebox and then barebox to load the kernel?
> And to run this image in QEMU will this boot loader not influence the system?

We use at91bootstrap and u-boot to boot a AT91SAM9G20-EK and our own
hardware, too. We made a few changes. For at91bootstrap this includes
adding IDs for the RAM we use on our boards. For u-boot there's a little
more for our own hardware, but board files for at91sam9263-ek are
included in current u-boot, you should get along with those.

> And the last one (sorry that I puncture you with my questions)At the
> moment I can not understand what will happen if I would change for
> example the memory. How can I tell that to the controller/ kernel?

You would have to patch at91bootstrap and u-boot. The best thing
however would be not to change the board files for at91sam9263-ek but to
copy these and edit your new board files. I'm not sure about
at91bootstrap but at least u-boot documentation recommends and describes
this.

HTH & Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2012-06-28  7:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28  6:42 Stutz Sven
2012-06-28  7:02 ` Robert Schwebel
2012-06-28  7:52 ` Alexander Dahl [this message]
2012-06-28  8:21   ` Stutz Sven
2012-06-28 13:35   ` Stutz Sven
2012-07-13  9:01     ` Stutz Sven
2012-07-13  9:10       ` Juergen Beisert
2012-06-28 18:44 ` Remy Bohmer
2012-08-01  9:15 [ptxdist] AT91SAM9263-EK Stutz Sven
2012-08-01  9:24 ` Thomas Petazzoni
2012-08-01 18:29   ` Stutz Sven

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=b82fd62bb0ecc8daaf9891b2aede8a80@idefix.lespocky.dyndns.org \
    --to=post@lespocky.de \
    --cc=ptxdist@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