qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: "Ben Dooks" <ben@fluff.org>, "Cédric Le Goater" <clg@kaod.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Alistair Francis <alistair@alistair23.me>,
	Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>,
	qemu-block@nongnu.org, qemu-devel@nongnu.org,
	Michael Walle <michael@walle.cc>
Subject: Re: [PATCH] m25p80: Add the is25wp256 SFPD table
Date: Tue, 27 Dec 2022 08:31:54 +0200	[thread overview]
Message-ID: <b00bb842-a9e6-fa5c-94d9-876c241be600@linaro.org> (raw)
In-Reply-To: <20221225121850.4bjnskmlhsot54cf@hetzy.fluff.org>



On 25.12.2022 14:18, Ben Dooks wrote:
> On Wed, Dec 21, 2022 at 06:36:02PM +0100, Cédric Le Goater wrote:
>> On 12/21/22 13:22, Guenter Roeck wrote:
>>> Generated from hardware using the following command and then padding
>>> with 0xff to fill out a power-of-2:
>>> 	xxd -p /sys/bus/spi/devices/spi0.0/spi-nor/sfdp
>>>
>>> Cc: Michael Walle <michael@walle.cc>
>>> Cc: Tudor Ambarus <tudor.ambarus@linaro.org>
>>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>>
>> Reviewed-by: Cédric Le Goater <clg@kaod.org>
> 
> If SFDP is a standard, couldn't we have an function to generate it from
> the flash parameters?
> 

No, it's not practical as you have to specify all the flash parameters
at flash declaration.


  reply	other threads:[~2022-12-27 14:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 12:22 [PATCH] m25p80: Add the is25wp256 SFPD table Guenter Roeck
2022-12-21 17:36 ` Cédric Le Goater
2022-12-25 12:18   ` Ben Dooks
2022-12-27  6:31     ` Tudor Ambarus [this message]
2023-01-02 13:53       ` Cédric Le Goater
2023-01-02 15:43         ` Michael Walle
2023-01-02 16:23           ` Guenter Roeck
2023-01-02 17:42             ` Michael Walle
2023-01-02 18:49               ` Guenter Roeck
2023-01-02 19:58                 ` Michael Walle

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=b00bb842-a9e6-fa5c-94d9-876c241be600@linaro.org \
    --to=tudor.ambarus@linaro.org \
    --cc=alistair@alistair23.me \
    --cc=ben@fluff.org \
    --cc=clg@kaod.org \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=linux@roeck-us.net \
    --cc=michael@walle.cc \
    --cc=qemu-block@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).