public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Porting to Broadcom BCM7038 (Hermes board)
Date: Thu, 20 Aug 2009 11:41:59 +0200	[thread overview]
Message-ID: <20090820094159.BDB3B833DBD2@gemini.denx.de> (raw)
In-Reply-To: <574bb010908200229m7da12930s39f7bc40a2384f1d@mail.gmail.com>

Dear Peter Belm,

In message <574bb010908200229m7da12930s39f7bc40a2384f1d@mail.gmail.com> you wrote:
>
> > That's not quite correct. IIRC, the "purple" board also uses a 64bit
> > MIPS processor (5Kc). So it's "just" anothe rnew board port.
> 
> The core in the BCM7038 is a 5Kf, I'm not sure how the minor revision
> effects something like UBoot, would any registers be different? As for it

Well, _all_ hardware differences affect U-Boot. You will need a really
detailed understanding of the processor and your board.

> being 64bit, the current bootloader is being compiled with a 32bit version
> of mipsel-uclibc-gcc, so it runs 32bit code fine. Would this be easier, or

Right. That's what we do in case of the "purple" board, too.

> does the fact it's a 64bit processor mean there's other changes which need
> to be taken into account in UBoot?

This obviously depends on your hardware design. We cannot answer this
question.

> Ok I think I get it now, in the cpu directory goes the code specific for
> bringing up the cpu, using the cache, etc. So the board directory would
> contain code for accessing the flash, init'ing memory, etc. And drivers
> would go into drivers/ as you said.

Assuming you use standard flash chips, no code to access the flash
should co to the board directory. You should use the existing standard
drivers instead.

> There's one fundamental thing I still need to get sorted in my head, what
> exactly is the role of UBoot? Is it just there to assist in creating a
> bootloader? So the cpu code would do the main bringup, board specific code

U-Boot _is_ the boot loader.

> would init the memory then use drivers provided by UBoot to access what it
> needs to load the kernel, then calls code in UBoot to start it? Or does
> UBoot perform a more invasive role than that?

All the tasks you mention here are performed by U-Boot. U-Boot _is_
the boot loader.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Microsoft Multitasking:
                     several applications can crash at the same time.

  reply	other threads:[~2009-08-20  9:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18 13:32 [U-Boot] Porting to Broadcom BCM7038 (Hermes board) Peter Belm
2009-08-19 16:13 ` Detlev Zundel
2009-08-19 19:19   ` Wolfgang Denk
2009-08-20  9:29     ` Peter Belm
2009-08-20  9:41       ` Wolfgang Denk [this message]
2009-08-20  9:47         ` Peter Belm
2009-08-20 11:18           ` Detlev Zundel
2009-08-20 11:04     ` Detlev Zundel

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=20090820094159.BDB3B833DBD2@gemini.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.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