From: "Nicolas DET"<nd@bplan-gmbh•de>
To: "Benjamin Herrenschmidt"<benh@kernel•crashing.org>,
"Nicolas DET"<nd@bplan-gmbh•de>,
"Matt Sealey"<matt@genesi-usa•com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs•org>,
Paul Mackerras <paulus@samba•org>
Subject: Re: EFIKA vs. CHRP platform
Date: Sat, 28 Oct 2006 15:41:54 +0200 (MEST) [thread overview]
Message-ID: <200610281341.k9SDfsqF020068@post.webmailer.de> (raw)
----- original message --------
Subject: EFIKA vs. CHRP platform
Sent: Sat, 28 Oct 2006
From: "Benjamin Herrenschmidt" <benh@kernel•crashing.org>
>=20
> - I'm not sure using RTAS for PCI config space is a very good idea.
> We'll need native mpc52xx_pci.c anyway, so we can juse use it for Efika
> as well instead of taking the massive overhead of RTAS calls on PCI
> config space accesses.
>=20
Compiling...
Efika will use as far as possible RTAS.
Bye
next reply other threads:[~2006-10-28 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-28 13:41 Nicolas DET [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-28 5:13 EFIKA vs. CHRP platform Benjamin Herrenschmidt
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=200610281341.k9SDfsqF020068@post.webmailer.de \
--to=nd@bplan-gmbh$(echo .)de \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=matt@genesi-usa$(echo .)com \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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