public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH]: cmd: part: add part block command
Date: Tue, 2 Jun 2020 14:30:59 -0400	[thread overview]
Message-ID: <20200602183059.GR21630@bill-the-cat> (raw)
In-Reply-To: <CAJAoKi_UKkZAqgYO1c6F8PAZ9_Rm1r4VoMGhJPprR7Kfh-o4mA@mail.gmail.com>

On Tue, Jun 02, 2020 at 11:08:19AM -0700, razvan becheriu wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> setexpr can compute the divide/multiply part, but we still need to get the
> partition block size somehow.
> 
> I know that this is 0x200 by default, but we can not hardcode that in the
> scripts. we should read that from the partition info.

So there's plenty of examples today of hard-coding that value.  Are you
worried about a potential future change or an exists today problem you
can't otherwise determine the hardware revision of at run-time?  Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200602/97f83999/attachment.sig>

  reply	other threads:[~2020-06-02 18:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 10:20 [PATCH]: cmd: part: add part block command razvan.becheriu at gmail.com
2020-06-01 10:20 ` [PATCH] cmd: part: Add 'block' sub-command razvan.becheriu at gmail.com
2020-06-02 17:55   ` Tom Rini
2020-06-02 17:55 ` [PATCH]: cmd: part: add part block command Tom Rini
2020-06-02 18:08   ` razvan becheriu
2020-06-02 18:30     ` Tom Rini [this message]
2020-06-02 18:36     ` razvan becheriu
2020-06-02 18:51       ` Tom Rini
2020-06-02 19:23         ` razvan becheriu
2020-06-05 18:01           ` Tom Rini

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=20200602183059.GR21630@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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