qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
To: Marcin Krzeminski <mar.krzeminski@gmail.com>
Cc: qemu-devel@nongnu.org, peter.maydell@linaro.org,
	qemu-arm@nongnu.org, clg@kaod.org
Subject: Re: [Qemu-devel] [PATCH v3 3/3] block: m25p80: Improve 1GiB Micron flash definition
Date: Mon, 9 Jan 2017 12:10:38 +0100	[thread overview]
Message-ID: <20170109111038.GI14990@toto> (raw)
In-Reply-To: <20170108083854.5006-4-mar.krzeminski@gmail.com>

On Sun, Jan 08, 2017 at 09:38:54AM +0100, Marcin Krzeminski wrote:
> n25q00 and mt25q01 devices share the same JEDEC ID. The difference
> between those two devices is number of dies and one bit in extended
> JEDEC bytes. This commit adds proper entry for both devices by
> introduction the number of dies and and new 25q00 entries.
> 
> Signed-off-by: Marcin Krzeminski <mar.krzeminski@gmail.com>

Reviewed-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>


> ---
>  hw/block/m25p80.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/hw/block/m25p80.c b/hw/block/m25p80.c
> index a9b025b..fb5cef3 100644
> --- a/hw/block/m25p80.c
> +++ b/hw/block/m25p80.c
> @@ -242,8 +242,10 @@ static const FlashPartInfo known_devices[] = {
>      { INFO("n25q128",     0x20ba18,      0,  64 << 10, 256, 0) },
>      { INFO("n25q256a",    0x20ba19,      0,  64 << 10, 512, ER_4K) },
>      { INFO("n25q512a",    0x20ba20,      0,  64 << 10, 1024, ER_4K) },
> -    { INFO("mt25ql01g",   0x20ba21,      0,  64 << 10, 2048, ER_4K) },
> -    { INFO("mt25qu01g",   0x20bb21,      0,  64 << 10, 2048, ER_4K) },
> +    { INFO_STACKED("n25q00",    0x20ba21, 0x1000, 64 << 10, 2048, ER_4K, 4) },
> +    { INFO_STACKED("n25q00a",   0x20bb21, 0x1000, 64 << 10, 2048, ER_4K, 4) },
> +    { INFO_STACKED("mt25ql01g", 0x20ba21, 0x1040, 64 << 10, 2048, ER_4K, 2) },
> +    { INFO_STACKED("mt25qu01g", 0x20bb21, 0x1040, 64 << 10, 2048, ER_4K, 2) },
>  
>      /* Spansion -- single (large) sector size only, at least
>       * for the chips listed here (without boot sectors).
> -- 
> 2.9.3
> 

  parent reply	other threads:[~2017-01-09 14:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-08  8:38 [Qemu-devel] [PATCH v3 0/3] block: m25p80: Improve mt25qu01g chip model Marcin Krzeminski
2017-01-08  8:38 ` [Qemu-devel] [PATCH v3 1/3] block: m25p80: Add Quad Page Program 4byte Marcin Krzeminski
2017-01-08  8:38 ` [Qemu-devel] [PATCH v3 2/3] block: m25p80: Introduce die erase command Marcin Krzeminski
2017-01-09  8:14   ` Cédric Le Goater
2017-01-09 11:10   ` Edgar E. Iglesias
2017-01-09 11:44     ` Marcin Krzemiński
2017-01-09 15:05       ` Edgar E. Iglesias
2017-01-08  8:38 ` [Qemu-devel] [PATCH v3 3/3] block: m25p80: Improve 1GiB Micron flash definition Marcin Krzeminski
2017-01-09  8:14   ` Cédric Le Goater
2017-01-09 11:10   ` Edgar E. Iglesias [this message]
2017-01-16 16:48 ` [Qemu-devel] [PATCH v3 0/3] block: m25p80: Improve mt25qu01g chip model Peter Maydell

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=20170109111038.GI14990@toto \
    --to=edgar.iglesias@xilinx.com \
    --cc=clg@kaod.org \
    --cc=mar.krzeminski@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.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).