From: Michael Walle <firstname.lastname@example.org>
To: Alexander Sverdlin <email@example.com>
Tudor Ambarus <firstname.lastname@example.org>,
Pratyush Yadav <email@example.com>,
Miquel Raynal <firstname.lastname@example.org>,
Richard Weinberger <email@example.com>,
Vignesh Raghavendra <firstname.lastname@example.org>,
Subject: Re: [PATCH] mtd: spi-nor: mt25qu: Ignore 6th ID byte
Date: Tue, 23 Nov 2021 09:14:18 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
Am 2021-11-23 08:45, schrieb Alexander Sverdlin:
> On 22/11/2021 16:05, Michael Walle wrote:
>>>>> Ignore 6th ID byte, secure version of mt25qu256a has 0x73 as 6th
>> You don't have the non-security part by chance?
> Unfortunately no. And this is exactly the trigger for this patch:
> one can get "secure" parts from Micron even though these "features" are
>> Mh, I'm undecided whether we should just duplicate the entry or if we
>> should ignore the last byte ("Device configuration information", where
>> is standard). The commit which introduced the flash was 7f412111e276b.
> Some people ask themselves why this table keeps growing if there is
> I see the point in fixups, but maybe at some point we will be able to
> some devices just out of the box?
Are these features detectable by SFDP? Without knowing anything, as you
my former question, I'd say no. So there will be two flashes, one with
features and one without, both presumably have the same SFDP. Thus we'd
these two entries anyway if we ever support these features. I get that
might be under NDA, but then talk to Micron; I for myself can't get a
>> Can you elaborate on the 0x73? Is that a bitmask? If it was an
>> I'd assumed it would be 01h (or some smaller value).
> This "security addendum" where one need NDA just says "73h = Secure".
> There is no explanation for it and no other variants.
> I'd really suggest to try to autodetect whatever features are going to
> supported from this chip and only duplicate the entry if this
There is a bigger patch series  from Tudor which you can try. You'd
respin your patch against that anyway.
Linux MTD discussion mailing list
next prev parent reply other threads:[~2021-11-23 8:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 8:04 [PATCH] mtd: spi-nor: mt25qu: Ignore 6th ID byte Alexander A Sverdlin
2021-11-19 21:19 ` Michael Walle
2021-11-22 7:06 ` Alexander Sverdlin
2021-11-22 15:05 ` Michael Walle
2021-11-23 7:45 ` Alexander Sverdlin
2021-11-23 8:14 ` Michael Walle [this message]
2021-11-23 12:40 ` Alexander Sverdlin
2021-11-23 14:01 ` Michael Walle
2021-11-23 16:14 ` Tudor.Ambarus
2021-11-23 12:13 ` Alexander Sverdlin
2021-11-23 17:42 ` Pratyush Yadav
2021-11-25 7:26 ` Alexander Sverdlin
2021-11-30 9:49 ` Pratyush Yadav
2022-07-18 15:03 ` Tudor.Ambarus
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).