From: Benjamin Herrenschmidt <bh40@calva.net>
To: Adrian Cox <apc@agelectronics.co.uk>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Going from 2.2.12 to 2.2.17pre10
Date: Tue, 11 Jul 2000 12:17:14 +0200 [thread overview]
Message-ID: <20000711101714.9717@mailhost.mipsys.com> (raw)
In-Reply-To: <396AEAC7.D8CACCB2@agelectronics.co.uk>
>
>Residual data is useful for things like finding the memory size, and for
>chips designed inside Apple. For almost everything else Linux already
>contains a device tree, built by PCI probing when the kernel boots^*. I
>don't see much need for a parallel, architecture specific, device tree.
In the case of Apple HW, the OF device tree is the only way to know about:
- Interrupt routing & sense type (level/edge)
- Machine model (for the machine device-specific stuffs we have)
- Bits inside Apple ASICs (we could hard code everything, but that doesn't
sound like a good idea, and the device tree also provide things like the
MAC address of the eth chip)
- Firmware boot path (to setup the OF boot and configure the bootloader)
- PCI hierarchy with the Uni-N chip
- Memory size (of course)
- What else did I forget ?
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-11 10:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-06 13:27 Going from 2.2.12 to 2.2.17pre10 Michael Lundkvist
2000-07-06 13:54 ` Hollis Blanchard
2000-07-06 17:17 ` Gabriel Paubert
2000-07-06 17:32 ` Michael Lundkvist
2000-07-06 17:55 ` Gabriel Paubert
2000-07-06 22:23 ` Michael Lundkvist
2000-07-07 8:22 ` Gabriel Paubert
2000-07-07 8:55 ` Michael Lundkvist
2000-07-07 9:21 ` Gabriel Paubert
2000-07-07 9:47 ` Michael Lundkvist
2000-07-07 10:19 ` Gabriel Paubert
2000-07-08 0:08 ` Problem with de4x5 on an MVME-2400 Michael Lundkvist
2000-07-10 11:58 ` Gabriel Paubert
2000-07-12 13:01 ` Michael Lundkvist
2000-07-08 23:29 ` Going from 2.2.12 to 2.2.17pre10 Matt Porter
2000-07-09 6:12 ` Michael Lundkvist
2000-07-10 5:29 ` Matt Porter
2000-07-10 12:25 ` Gabriel Paubert
2000-07-11 5:57 ` Matt Porter
2000-07-11 9:37 ` Adrian Cox
2000-07-11 10:17 ` Benjamin Herrenschmidt [this message]
2000-07-11 12:57 ` Adrian Cox
2000-07-11 14:10 ` Claus
2000-07-11 19:15 ` Geert Uytterhoeven
2000-07-12 13:31 ` Benjamin Herrenschmidt
2000-07-13 11:17 ` Geert Uytterhoeven
2000-07-12 9:11 ` Timothy A. Seufert
2000-07-12 14:16 ` Matt Porter
2000-07-13 11:43 ` Gabriel Paubert
2000-07-13 14:12 ` Matt Porter
2000-07-12 12:52 ` Michael Lundkvist
2000-07-12 14:17 ` Matt Porter
2000-07-10 12:12 ` Gabriel Paubert
2000-07-11 6:12 ` Matt Porter
2000-07-11 10:48 ` Gabriel Paubert
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=20000711101714.9717@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=apc@agelectronics.co.uk \
--cc=linuxppc-dev@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).