All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Porter <porter@cox.net>
To: Khai Trinh <kqtrinh@yahoo.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Ebony bootloader
Date: Tue, 11 Jun 2002 19:51:30 -0700	[thread overview]
Message-ID: <20020611195130.C28767@home.com> (raw)
In-Reply-To: <20020611234337.46834.qmail@web11503.mail.yahoo.com>; from kqtrinh@yahoo.com on Tue, Jun 11, 2002 at 04:43:37PM -0700


On Tue, Jun 11, 2002 at 04:43:37PM -0700, Khai Trinh wrote:
>
> Does the Ebony board port implement a bootloader? What

It uses the "simple" bootloader.

> does the head_440.S file do in a nutshell?

init MMU and jump to start_kernel.

> If our custom board has peripheral devices hanging off
> the EBC0, how should I initilize them and where in the
> ebony port code? I browsed the source a little bit and
> see the ebony.c source. I believe this is where you
> add peripheral devices to the kernel. Am I right?

You can add then wherever you want, but ideally you would
create a <custom_board>.c with board specific I/O code.

> What is that ioremap64() anyway? Is this a kernel call
> or a called supported by the firmware?

Read Understanding Linux, Linux Device Drivers, and the
documentation in Documentation/ directory.  ioremap64()
is a version of ioremap() for >32-bit physical address
systems (440, 745x).

Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-06-12  2:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-11 23:43 Ebony bootloader Khai Trinh
2002-06-12  2:51 ` Matt Porter [this message]
2002-06-12  5:10   ` Paul Mackerras
2002-06-12 10:51     ` Matt Porter
2002-06-12 11:33   ` Khai Trinh
2002-06-15 15:10     ` Matt Porter

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=20020611195130.C28767@home.com \
    --to=porter@cox.net \
    --cc=kqtrinh@yahoo.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.