From: Olof Johansson <olof@lixom.net>
To: Nathan Lynch <ntl@pobox.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [BUG] flash failure with CONFIG_RTAS_FLASH=m
Date: Thu, 4 Jan 2007 18:04:06 -0600 [thread overview]
Message-ID: <20070104180406.6843ead3@localhost.localdomain> (raw)
In-Reply-To: <20070104234951.GJ6279@localdomain>
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.
-Olof
next prev parent reply other threads:[~2007-01-05 0:04 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 [this message]
2007-01-08 1:09 ` Michael Ellerman
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=20070104180406.6843ead3@localhost.localdomain \
--to=olof@lixom.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.com \
/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).