From: Johannes Berg <johannes@sipsolutions.net>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, Milton Miller <miltonm@bga.com>,
David Gibson <dwg@au1.ibm.com>
Subject: Re: PReP residual to device-tree converter
Date: Wed, 09 Jul 2008 13:29:12 +0200 [thread overview]
Message-ID: <1215602952.3670.39.camel@johannes.berg> (raw)
In-Reply-To: <1215600470.3670.35.camel@johannes.berg>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
On Wed, 2008-07-09 at 12:48 +0200, Johannes Berg wrote:
> > I would like people that have PReP machines to take a copy of
> > /proc/residual, run this program on it, and check that the output is
> > sane. If it isn't, or if it is missing bits, send me the residual
> > blob with a description of what's wrong in the generated dts.
>
> Here's the output from qemu:
[...]
Milton wanted iomem and ioports, I didn't manage to get userspace
working so I printed them in the kernel (hopefully correctly):
iomem:
c0000000-feffffff : PCI host bridge
c80000f0-c80000ff : 0000:00:01.0
ioports:
00000000-007fffff : PCI host bridge
00000000-0000001f : dma1
00000020-00000021 : 8259 (master)
00000040-0000005f : timer
00000080-0000008f : dma page reg
000000a0-000000a1 : 8259 (slave)
000000c0-000000df : dma2
000004d0-000004d1 : 8259 edge control
FWIW, my qemu command line was:
qemu-system-ppc -initrd initrd -kernel linux/arch/ppc/boot/images/zImage.prep -M prep -cpu 604 -serial stdio
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-07-09 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 6:25 PReP residual to device-tree converter Paul Mackerras
2008-07-09 10:47 ` Johannes Berg
2008-07-09 11:29 ` Johannes Berg [this message]
2008-07-09 11:33 ` Johannes Berg
2008-07-09 11:39 ` Johannes Berg
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=1215602952.3670.39.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=dwg@au1.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=miltonm@bga.com \
--cc=paulus@samba.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).