From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matt Sealey <matt@genesi-usa.com>
Cc: linuxppc-dev@ozlabs.org, David Woodhouse <dwmw2@infradead.org>,
paulus@samba.org
Subject: Re: [EFIKA] Really, don't pretend to be CHRP
Date: Fri, 18 Apr 2008 18:24:08 +1000 [thread overview]
Message-ID: <1208507048.6958.407.camel@pasglop> (raw)
In-Reply-To: <48076A00.1080608@genesi-usa.com>
On Thu, 2008-04-17 at 16:17 +0100, Matt Sealey wrote:
>
> I said the kernel has had braindead patches shoved into it that sort
> of
> obviate the need for the most heinous of crimes committed in the Efika
> device tree.
>
> The Linux kernel fixups don't add the CDM or XLB arbiter or many other
> components some out-of-mainline drivers will need (and should be able
> to just access without writing a fixup first) to map to work properly.
> Adding these will clean up things like the UART module, Sylvain's
> sleep
> patches will work on Efika, etc.
What about you guys fix the firmware once for all instead of spamming
our mailboxes ?
> > can't set environment variables from within Linux (and yes, we can
> > probably improve on that too, but we let them setenv for themselves,
> for
> > now).
>
> You really won't be improving on it because there's no reliable way to
> pass setenv back to the firmware from userland :D
They aren't in nvram ? If they are and using the standard OF CHRP
format, then we can.
Ben.
next prev parent reply other threads:[~2008-04-18 8:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 16:52 [EFIKA] Really, don't pretend to be CHRP David Woodhouse
2008-04-14 2:54 ` Grant Likely
2008-04-17 12:28 ` Matt Sealey
2008-04-17 14:37 ` David Woodhouse
2008-04-17 15:17 ` Matt Sealey
2008-04-17 16:37 ` David Woodhouse
2008-04-18 15:33 ` Matt Sealey
2008-04-19 0:53 ` Benjamin Herrenschmidt
2008-04-18 0:17 ` David Gibson
2008-04-18 8:24 ` Benjamin Herrenschmidt [this message]
2008-04-18 15:21 ` Matt Sealey
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=1208507048.6958.407.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=dwmw2@infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=matt@genesi-usa.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).