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.checko...@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 <th...@redhat.com>