linuxppc-dev.lists.ozlabs.org archive mirror
 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: Sat, 15 Jun 2002 08:10:21 -0700	[thread overview]
Message-ID: <20020615081021.A737@home.com> (raw)
In-Reply-To: <20020612113317.33359.qmail@web11508.mail.yahoo.com>; from kqtrinh@yahoo.com on Wed, Jun 12, 2002 at 04:33:17AM -0700


On Wed, Jun 12, 2002 at 04:33:17AM -0700, Khai Trinh wrote:
> Matt,
>
> Thanks for the info. I have a follow up question. I am
> trying to understand this whole embedded development
> in general and not really a Linux specific question.
> Are the board specific IO code setup to tell the
> kernel the presence of the individual peripheral
> devices on its bus (ie: the EBC0)? After that, a

Correct.  This is for cases where we want to write
a driver that is shared across multiple core and
board implementations.

> driver is required for each device attach to the EBC0?

Correct.

> Is this driver a driver communicates to the EBC0 or a
> driver communicates to the device thru the EBC0 device
> memory map? Or my whole understanding is out of whack?

It is a standalone kernel driver for the device connected
via the EBC.  There is no "driver" for the EBC itself.

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-15 15:10 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
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 [this message]

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=20020615081021.A737@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).