From: Stefan Weil <sw@weilnetz.de>
To: walimis <walimisdev@gmail.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for 1.3] pflash_cfi01: Suppress warning when Linux probes for AMD flash
Date: Mon, 26 Nov 2012 07:38:45 +0100 [thread overview]
Message-ID: <50B30E75.8030806@weilnetz.de> (raw)
In-Reply-To: <20121126053153.GA3127@walimis-DELL>
Am 26.11.2012 06:31, schrieb walimis:
> On Sat, Nov 24, 2012 at 11:03:13PM +0100, Stefan Weil wrote:
>> There are several ARM and MIPS boards which are manufactured with
>> either Intel (pflash_cfi01.c) or AMD (pflash_cfi02.c) flash memory.
>>
>> The Linux kernel supports both and first probes for AMD flash which
>> resulted in one or two warnings from the Intel flash emulation:
>>
>> pflash_write: Unimplemented flash cmd sequence (offset 0000000000000000, wcycle 0x0 cmd 0x0 value 0xf000f0)
>> pflash_write: Unimplemented flash cmd sequence (offset 0000000000000000, wcycle 0x0 cmd 0x0 value 0xf0)
> Hi Stefan,
>
> I ever submited a similar patch to mailing list:
> http://patchwork.ozlabs.org/patch/147886/
>
> Do you have a look at that patch to see whether it's sane for the
> different parts between mine and yours?
>
> Thanks,
> Liming Wang
Hi,
your patch is technically identical, but I think that your commit message
ismisleading: it implies that 0xff and 0xf0 are both specified in the
CFI specification for Intel flash memory (CFI 01). As far as I could see,
0xf0 is only a specified flash command sequence for AMD flash memory
(CFI 02).
That's why Linux uses it to detect that kind of flash memory.
If you resend your patch with a commit message and a comment in
the code which explains why 0xf0 needs handling in pflash_cfi01.c,
it can be committed IMHO.
Regards
Stefan
next prev parent reply other threads:[~2012-11-26 6:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 22:03 [Qemu-devel] [PATCH for 1.3] pflash_cfi01: Suppress warning when Linux probes for AMD flash Stefan Weil
2012-11-26 5:31 ` walimis
2012-11-26 6:38 ` Stefan Weil [this message]
2013-01-01 12:06 ` Aurelien Jarno
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=50B30E75.8030806@weilnetz.de \
--to=sw@weilnetz.de \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=walimisdev@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.