From: Richard Weinberger <richard@nod.at>
To: Cheng Ming Lin <linchengming884@gmail.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
chengzhihao1 <chengzhihao1@huawei.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Alvin Zhou <alvinzhou@mxic.com.tw>, leoyu <leoyu@mxic.com.tw>,
Cheng Ming Lin <chengminglin@mxic.com.tw>
Subject: Re: [PATCH 1/1] mtd: ubi: skip programming unused bits in ubi headers
Date: Fri, 7 Nov 2025 10:12:35 +0100 (CET) [thread overview]
Message-ID: <954318808.156230.1762506755899.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <CAAyq3Sb8-FRC+bZt_bEvOdBNVSN4xa5F_TpBbKF__HzhVPEpTw@mail.gmail.com>
----- Ursprüngliche Mail -----
> Von: "Cheng Ming Lin" <linchengming884@gmail.com>
>> Here I am reaching the limits of my UBI knowledge, so I would prefer
>> Richard to (in)validate what I am saying, but AFAIU, the VID header can
>> be literally anywhere in the page, not just at the start or end of a
>> subpage, so in the vid_hdr_shift I would expect some extra maths to
>> happen, no?
Good catch!
I had to read the code change twice to see the problem, though. :-S
> I understand your point now. If the VID header is not guaranteed to be
> at the start or end of a subpage, then yes, my current logic needs to be
> reworked to cover that case.
Yes. This can be configured using ubiattach --vid-hdr-offset ...
With nandsim you can test all kind of combinations.
Thanks,
//richard
prev parent reply other threads:[~2025-11-07 9:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 5:49 [PATCH 0/1] mtd: ubi: skip programming unused bits in ubi headers Cheng Ming Lin
2025-11-06 5:49 ` [PATCH 1/1] " Cheng Ming Lin
2025-11-06 9:10 ` Miquel Raynal
2025-11-06 9:45 ` Cheng Ming Lin
2025-11-07 6:31 ` Cheng Ming Lin
2025-11-07 8:23 ` Miquel Raynal
2025-11-07 8:28 ` Cheng Ming Lin
2025-11-07 9:12 ` Richard Weinberger [this message]
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=954318808.156230.1762506755899.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=alvinzhou@mxic.com.tw \
--cc=chengminglin@mxic.com.tw \
--cc=chengzhihao1@huawei.com \
--cc=leoyu@mxic.com.tw \
--cc=linchengming884@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox