From: Pratyush Yadav <pratyush@kernel.org>
To: "Michael Walle" <mwalle@kernel.org>
Cc: "Brian Norris" <computersforpeace@gmail.com>,
<linux-mtd@lists.infradead.org>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Pratyush Yadav" <pratyush@kernel.org>,
"Richard Weinberger" <richard@nod.at>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mtd: spi-nor: micron-st: Add n25q064a WP support
Date: Tue, 30 Jul 2024 13:24:15 +0200 [thread overview]
Message-ID: <mafs034nr2kdc.fsf@kernel.org> (raw)
In-Reply-To: <D32OADQF733D.3CVS3ZRPEBL2O@kernel.org> (Michael Walle's message of "Tue, 30 Jul 2024 08:51:05 +0200")
On Tue, Jul 30 2024, Michael Walle wrote:
> Hi,
>
> On Fri Jul 26, 2024 at 8:58 PM CEST, Brian Norris wrote:
>> These flash chips are used on Google / TP-Link / ASUS OnHub devices, and
>> OnHub devices are write-protected by default (same as any other
>> ChromeOS/Chromebook system). I've referred to datasheets, and tested on
>> OnHub devices.
>
> Out of curiosity, there is also a hardware write protect switch
> somehow, right? At least that's my understanding how verify boot
> works.
>
>>
>> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
>
> This looks good:
> Reviewed-by: Michael Walle <mwalle@kernel.org>
Applied to spi-nor/next. Thanks, both!
--
Regards,
Pratyush Yadav
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Pratyush Yadav <pratyush@kernel.org>
To: "Michael Walle" <mwalle@kernel.org>
Cc: "Brian Norris" <computersforpeace@gmail.com>,
<linux-mtd@lists.infradead.org>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Pratyush Yadav" <pratyush@kernel.org>,
"Richard Weinberger" <richard@nod.at>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mtd: spi-nor: micron-st: Add n25q064a WP support
Date: Tue, 30 Jul 2024 13:24:15 +0200 [thread overview]
Message-ID: <mafs034nr2kdc.fsf@kernel.org> (raw)
In-Reply-To: <D32OADQF733D.3CVS3ZRPEBL2O@kernel.org> (Michael Walle's message of "Tue, 30 Jul 2024 08:51:05 +0200")
On Tue, Jul 30 2024, Michael Walle wrote:
> Hi,
>
> On Fri Jul 26, 2024 at 8:58 PM CEST, Brian Norris wrote:
>> These flash chips are used on Google / TP-Link / ASUS OnHub devices, and
>> OnHub devices are write-protected by default (same as any other
>> ChromeOS/Chromebook system). I've referred to datasheets, and tested on
>> OnHub devices.
>
> Out of curiosity, there is also a hardware write protect switch
> somehow, right? At least that's my understanding how verify boot
> works.
>
>>
>> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
>
> This looks good:
> Reviewed-by: Michael Walle <mwalle@kernel.org>
Applied to spi-nor/next. Thanks, both!
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2024-07-30 11:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 18:58 [PATCH] mtd: spi-nor: micron-st: Add n25q064a WP support Brian Norris
2024-07-26 18:58 ` Brian Norris
2024-07-30 6:51 ` Michael Walle
2024-07-30 6:51 ` Michael Walle
2024-07-30 11:24 ` Pratyush Yadav [this message]
2024-07-30 11:24 ` Pratyush Yadav
2024-07-30 11:33 ` Tudor Ambarus
2024-07-30 11:33 ` Tudor Ambarus
2024-07-30 17:28 ` Brian Norris
2024-07-30 17:28 ` Brian Norris
2024-07-31 8:51 ` Tudor Ambarus
2024-07-31 8:51 ` Tudor Ambarus
2024-07-31 9:05 ` Michael Walle
2024-07-31 9:05 ` Michael Walle
2024-07-31 17:31 ` Brian Norris
2024-07-31 17:31 ` Brian Norris
2024-08-05 9:01 ` Michael Walle
2024-08-05 9:01 ` Michael Walle
2024-07-31 17:10 ` Brian Norris
2024-07-31 17:10 ` Brian Norris
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=mafs034nr2kdc.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=richard@nod.at \
--cc=tudor.ambarus@linaro.org \
--cc=vigneshr@ti.com \
/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.