From: Michael Ellerman <michael@ellerman.id.au>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org, Nathan Lynch <ntl@pobox.com>
Subject: Re: [BUG] flash failure with CONFIG_RTAS_FLASH=m
Date: Mon, 08 Jan 2007 12:09:04 +1100 [thread overview]
Message-ID: <1168218544.30064.3.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <20070104180406.6843ead3@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On Thu, 2007-01-04 at 18:04 -0600, Olof Johansson wrote:
> On Thu, 4 Jan 2007 17:49:51 -0600 Nathan Lynch <ntl@pobox.com> wrote:
>
> > The problem doesn't happen if CONFIG_RTAS_FLASH=y.
> >
> > What's the best way to fix this? Should rtas_firmware_flash_list be
> > defined in some non-modular code and exported?
>
> Makes sense to me.
>
> You could allocate it dynamically really early (i.e. lmb_alloc) since
> that's the only allocator that we can give limits to where in the
> address range it can allocate. It seems to be overkill in this case
> though, it's just a page worth of data.
There's the ZONE stuff, but it doesn't help us because our ZONE_DMA ==
all of ram - we'd need to add another ZONE below that, which is generic
code :/
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-01-08 1:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 23:49 [BUG] flash failure with CONFIG_RTAS_FLASH=m Nathan Lynch
2007-01-05 0:04 ` Olof Johansson
2007-01-08 1:09 ` Michael Ellerman [this message]
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=1168218544.30064.3.camel@concordia.ozlabs.ibm.com \
--to=michael@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.com \
--cc=olof@lixom.net \
/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).