From: Dan Malek <dan@netx4.com>
To: Sebastien Articlaux <sebastien_articlaux@yahoo.com>
Cc: embedded linuxppc <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: struct bd_info
Date: Fri, 03 Mar 2000 01:24:27 -0500 [thread overview]
Message-ID: <38BF5A9B.3C7BB222@netx4.com> (raw)
In-Reply-To: 20000303143138.28215.qmail@web208.mail.yahoo.com
Sebastien Articlaux wrote:
> Someone could explain to me what to put on the
> structure board info?
I created that when I did the original 8xx port of Linux/PPC.
It served as a model to provide some information to an
embedded kernel. Normally, Linux/PPC gets lots of information
from the OF data structures, and in the embedded systems
we don't have such capability.
> ie , I just want to know, for instance, if ,for the
> size of DRAM memory I must put the real size
> of DRAM in hex,
Hex, decimal, octal, it doesn't really matter :-).
It has to be the size of DRAM (or the size you offer
Linux to use). It is used during the Linux memory
initialization.
> .... or if it's a offset in relation with
> the chipset select or something else...
It was modelled after the data structure EPPC-Bug provides
to a program when it is started. The board information
structure are not all identical, although I would like them
that way. It includes information about memory location and
sizes, processor/bus speed, console baud rate, Ethernet address,
and so on. If you have a system with discontiguous memory
spaces, you will have to modify the structure to accomodate this.
I would recommend making arrays for the start and size information.
For systems where I wrote the boot rom, it creates the board
information structure and passes it to the Linux image. Most
other boards create a board information structure in
arch/ppc/mbxboot/embed_config.c and pass that to the Linux kernel.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-03-03 6:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-03 14:31 struct bd_info Sebastien Articlaux
2000-03-03 6:24 ` Dan Malek [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=38BF5A9B.3C7BB222@netx4.com \
--to=dan@netx4.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=sebastien_articlaux@yahoo.com \
/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.