From: Gabriel Paubert <paubert@iram.es>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH 3/3] First cut at PReP support for arch/powerpc
Date: Tue, 3 Jul 2007 11:51:14 +0200 [thread overview]
Message-ID: <20070703095114.GA31118@iram.es> (raw)
In-Reply-To: <f778cbc9a05aafa7527bd14f9259aad2@kernel.crashing.org>
On Mon, Jul 02, 2007 at 01:51:42PM +0200, Segher Boessenkool wrote:
> >>+ external-control;
> >>
> >>Really?
> >
> >Well, is anybody actually using eciwx/ecowx?
>
> That's not the point -- the device tree should only
> say "external-control" if the CPU actually supports
> it; AFAIK, that's 601 only.
I wonder whether you are mixing up external control
and direct-store segments (the "T" bit in segment registers).
>From my docs, external control has been supported by many
processors, up to many variants of the 750 and even 7440/7450.
Now I've never seen any hardware which could make use of these
instructions (you'd need a device on the processor bus that
reacts to the special bus cycles generated by the ec[io]wx
instructions, since no host bridge I've ever met handles them.
I've not seen support for external control in the Linux kernel
either (you'd need to setup the EAR SPR and probablly to modify
it on context switches).
OTOH, the direct-store segments were only implemented in the
original 601, 603 (not 603e) and 604 processors (can't remember
about the 604e) and even then the 601 had special features
in this area.
>
> >>+ pci@80000000 {
> >>+ device_type = "pci";
> >>+ compatible = "prep";
> >>
> >>Is that specific enough?
> >
> >On the MVME5100, actually the mapping is more CHRP like, and PCI I/O
> >space is smaller and at a higher address.
>
> Right, so it's not; "compatible" should specify the
> model of PCI host bridge, instead.
Well, the PCI host bridge is reprogrammable in a very flexible way
and and I actually wrote a boot loader that reprograms it the
way I wanted address space to look like. I shall send it to
you in a PM (it is quite big, it includes an x86 emulator
which is able to initialize the VGA PMC modules I have by
running the BIOS).
Regards,
Gabriel
next prev parent reply other threads:[~2007-07-03 9:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 6:53 [PATCH 0/3] PReP support David Gibson
2007-06-27 6:54 ` [PATCH 1/3] Abolish unused ucBoardRev variables David Gibson
2007-06-27 6:54 ` [PATCH 2/3] Make more OF-related bootwrapper functions available to non-OF platforms David Gibson
2007-06-28 8:44 ` Segher Boessenkool
2007-06-27 7:10 ` [PATCH 3/3] First cut at PReP support for arch/powerpc David Gibson
2007-06-27 11:22 ` Milton Miller
2007-06-27 11:29 ` udbg_16550.c and legacy_serial.c Milton Miller
2007-06-28 0:38 ` [PATCH 3/3] First cut at PReP support for arch/powerpc David Gibson
2007-06-28 8:59 ` Segher Boessenkool
2007-06-28 10:00 ` Gabriel Paubert
2007-07-02 11:51 ` Segher Boessenkool
2007-07-03 9:51 ` Gabriel Paubert [this message]
2007-07-03 12:49 ` Segher Boessenkool
2007-07-03 2:26 ` Tom Gall
2007-07-03 6:50 ` Ulrich Teichert
2007-08-03 6:35 ` David Gibson
2007-08-03 15:24 ` Jon Loeliger
2007-08-06 19:43 ` Segher Boessenkool
2007-08-06 19:42 ` Segher Boessenkool
2007-07-18 1:31 ` David Gibson
2007-07-18 15:55 ` Segher Boessenkool
2007-08-03 6:43 ` David Gibson
2007-08-06 19:37 ` Segher Boessenkool
-- strict thread matches above, loose matches on Subject: below --
2007-08-03 21:55 Yoder Stuart-B08248
2007-08-06 4:02 ` David Gibson
2007-08-06 19:45 ` Segher Boessenkool
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=20070703095114.GA31118@iram.es \
--to=paubert@iram.es \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=segher@kernel.crashing.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).