From: Michael Ellerman <michael@ellerman.id.au>
To: John Rose <johnrose@austin.ibm.com>
Cc: External List <linuxppc-dev@ozlabs.org>,
Michael Neuling <mikey@neuling.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] powerpc: force 4k update_flash block and list sizes
Date: Wed, 08 Nov 2006 15:41:00 +1100 [thread overview]
Message-ID: <1162960860.20271.13.camel@localhost.localdomain> (raw)
In-Reply-To: <1162960202.14254.3.camel@sinatra.austin.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
On Tue, 2006-11-07 at 22:30 -0600, John Rose wrote:
> > kmem_cache_destroy doesn't return anything.
>
> Good call! How's this:
>
> The enablement of 64k pages on POWER platforms exposed a quirk in the RTAS
> mechanism for updating firmware. RTAS assumes 4k for flash block and list
> sizes, and use of any other sizes results in a failure.
>
> This patch changes the rtas_flash module to force the use of 4k memory block
> and list sizes when preparing and sending a firmware image to RTAS. It also
> changes rtas_flash to use a slab cache to ensure 4k alignment of flash block
> data. Such alignment is a documented requirement.
Just being picky .. but why did you decide to use the slab cache? Does
it make the code neater? I would have thought you could guarantee 4k
alignment some other way, and it seems slightly odd to use the slab
cache for something you only do once ..
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 --]
next prev parent reply other threads:[~2006-11-08 4:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 23:53 [PATCH] powerpc: force 4k update_flash block and list sizes John Rose
2006-11-08 2:06 ` Michael Neuling
2006-11-08 4:30 ` John Rose
2006-11-08 4:39 ` Michael Neuling
2006-11-08 16:07 ` John Rose
2006-11-08 4:41 ` Michael Ellerman [this message]
2006-11-08 9:28 ` Arnd Bergmann
2006-11-08 22:40 ` 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=1162960860.20271.13.camel@localhost.localdomain \
--to=michael@ellerman.id.au \
--cc=johnrose@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--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).