All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Stephen Checkoway" <stephen.checkoway@oberlin.edu>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Kevin Wolf" <kwolf@redhat.com>, "Max Reitz" <mreitz@redhat.com>,
	"open list:Block layer core" <qemu-block@nongnu.org>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Laszlo Ersek" <lersek@redhat.com>,
	"Laurent Vivier" <lvivier@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 05/10] block/pflash_cfi02: Implement nonuniform sector sizes
Date: Thu, 18 Apr 2019 06:25:29 +0200	[thread overview]
Message-ID: <9e1b8e19-a40a-5070-0815-9e783435d542@redhat.com> (raw)
In-Reply-To: <20190417220147.67648-6-stephen.checkoway@oberlin.edu>

On 18/04/2019 00.01, Stephen Checkoway wrote:
> Some flash chips support sectors of different sizes. For example, the
> AMD AM29LV160DT has 31 64 kB sectors, one 32 kB sector, two 8 kB
> sectors, and a 16 kB sector, in that order. The AM29LV160DB has those in
> the reverse order.
> 
> The `num-blocks` and `sector-length` properties work exactly as they did
> before: a flash device with uniform sector lengths. To get non-uniform
> sector lengths for up to four regions, the following properties may be
> set
> - region 0. `num-blocks0` and `sector-length0`;
> - region 1. `num-blocks1` and `sector-length1`;
> - region 2. `num-blocks2` and `sector-length2`; and
> - region 3. `num-blocks3` and `sector-length3`.
> 
> If the uniform and nonuniform properties are set, then both must specify
> a flash device with the same total size. It would be better to disallow
> both being set, or make `num-blocks0` and `sector-length0` alias
> `num-blocks` and `sector-length`, but that would make testing currently
> impossible.
> 
> Signed-off-by: Stephen Checkoway <stephen.checkoway@oberlin.edu>
> ---
>  hw/block/pflash_cfi02.c   | 177 +++++++++++++++++++++++++-----------
>  tests/pflash-cfi02-test.c | 185 ++++++++++++++++++++++++++++----------
>  2 files changed, 265 insertions(+), 97 deletions(-)

Acked-by: Thomas Huth <thuth@redhat.com>

  reply	other threads:[~2019-04-18  4:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17 22:01 [Qemu-devel] [PATCH v3 00/10] block/pflash_cfi02: Implement missing AMD pflash functionality Stephen Checkoway
2019-04-17 22:01 ` [Qemu-devel] [PATCH v3 01/10] block/pflash_cfi02: Add test for supported commands Stephen Checkoway
2019-04-18  4:47   ` Thomas Huth
2019-04-18 20:43     ` Stephen Checkoway
2019-04-18 20:43       ` Stephen Checkoway
2019-04-19  5:57       ` Thomas Huth
2019-04-19  5:57         ` Thomas Huth
2019-04-17 22:01 ` [Qemu-devel] [PATCH v3 02/10] block/pflash_cfi02: Refactor, NFC intended Stephen Checkoway
2019-04-17 22:01 ` [Qemu-devel] [PATCH v3 03/10] block/pflash_cfi02: Fix command address comparison Stephen Checkoway
2019-04-18  4:22   ` Thomas Huth
2019-04-17 22:01 ` [Qemu-devel] [PATCH v3 04/10] block/pflash_cfi02: Implement intereleaved flash devices Stephen Checkoway
2019-04-18  4:23   ` Thomas Huth
2019-04-17 22:01 ` [Qemu-devel] [PATCH v3 05/10] block/pflash_cfi02: Implement nonuniform sector sizes Stephen Checkoway
2019-04-18  4:25   ` Thomas Huth [this message]
2019-04-17 22:01 ` [Qemu-devel] [PATCH v3 06/10] block/pflash_cfi02: Fix CFI in autoselect mode Stephen Checkoway
2019-04-18  4:28   ` Thomas Huth
2019-04-17 22:01 ` [Qemu-devel] [PATCH v3 07/10] block/pflash_cfi02: Fix reset command not ignored during erase Stephen Checkoway
2019-04-17 22:01 ` [Qemu-devel] [PATCH v3 08/10] block/pflash_cfi02: Implement multi-sector erase Stephen Checkoway
2019-04-18  4:52   ` Thomas Huth
2019-04-17 22:01 ` [Qemu-devel] [PATCH v3 09/10] block/pflash_cfi02: Implement erase suspend/resume Stephen Checkoway
2019-04-18  4:54   ` Thomas Huth
2019-04-17 22:01 ` [Qemu-devel] [PATCH v3 10/10] block/pflash_cfi02: Use the chip erase time specified in the CFI table Stephen Checkoway

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=9e1b8e19-a40a-5070-0815-9e783435d542@redhat.com \
    --to=thuth@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lersek@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stephen.checkoway@oberlin.edu \
    /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.