mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Mathieu Anquetin <mathieu.anquetin@groupe-cahors.com>
To: barebox@lists.infradead.org
Subject: Lowlevel questions
Date: Mon, 18 Nov 2013 11:25:27 +0100	[thread overview]
Message-ID: <5289EB17.1030802@groupe-cahors.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 883 bytes --]

Hi,

I am currently trying to port Barebox to a new ARM-based machine and I
am facing some questions concerning low level initialization (before
relocation to RAM). Reading the header files, I came across 3 functions
that may be of interest during startup but I can't find an example of
them being called, they are :
    - board_init
    - dram_init
    - board_init_lowlevel

AFAIK, every other board in the barebox tree defines functions that
resemble those but never implements them directly. Can someone confirm
that this is the case ? Should I do the same or is it a new
implementation that future boards may use ?

Thanks in advance,
-- 

*Mathieu ANQUETIN*

/Software Engineer
/


Logo CAHORS Mail


CRDE
ZI des Grands Camps
46090 MERCUES
Tél. : +33 (0)5 65 30 38 27
*www.groupe-cahors.com*


*GROUPE CAHORS soutient le pacte mondial.*



[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 966 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2013-11-18 10:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 10:25 Mathieu Anquetin [this message]
2013-11-19  9:51 ` Sascha Hauer
2013-11-19 10:24   ` Alexander Aring
2013-11-19 11:01   ` Mathieu Anquetin
2013-11-19 11:31     ` 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=5289EB17.1030802@groupe-cahors.com \
    --to=mathieu.anquetin@groupe-cahors.com \
    --cc=barebox@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