From: Robert Schwebel <r.schwebel@pengutronix.de>
To: ptxdist@pengutronix.de, stutzsven@web.de
Subject: Re: [ptxdist] AT91SAM9263-ek
Date: Thu, 28 Jun 2012 09:02:35 +0200 [thread overview]
Message-ID: <20120628070235.GN3199@pengutronix.de> (raw)
In-Reply-To: <4FEBFCD7.7060607@web.de>
Hi,
On Thu, Jun 28, 2012 at 08:42:31AM +0200, Stutz Sven wrote:
> I have an evaluation board (at91sam9263-ek Rev. B) from Atmel and I am
> trying now to get a customized OS running on this board.
>
> As I read in the manual, that I need for that purpose a special BSP
> for this eval. board. But where can I get this BSP from or from which
> example BSP can I derive this information to built it from scratch?
I think there is no public BSP from us for that board, although we have
worked a lot with the atmel chips in the past (but usually on custom
hardware). You can basically use any BSP for a start and adapt it to
your hardware needs.
Atmel plays nicely with the mainline kernel, so please start with 3.4.x
and check how far you come.
> 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?
Currently yes.
> And to run this image in QEMU will this boot loader not influence
> the system?
It depends on what you want to achieve by running in QEMU. As a rule of
thumb, qemu is often a good thing when it comes to system issues, but if
you care about hardware, you should run on hardware.
> 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?
This is modelled in the open firmware devicetree. Your bootloader has to
know the information and put it into the right location.
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 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-06-28 7:02 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 [this message]
2012-06-28 7:52 ` Alexander Dahl
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=20120628070235.GN3199@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=stutzsven@web.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