From: Marek Vasut <marek.vasut@mailbox.org>
To: Peter Robinson <pbrobinson@gmail.com>,
Detlev Casanova <detlev.casanova@collabora.com>
Cc: u-boot@lists.denx.de,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
Hai Pham <hai.pham.ud@renesas.com>,
Tam Nguyen <tam.nguyen.xa@renesas.com>,
Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH v4 0/6] Introduce the sysinfo command
Date: Tue, 8 Aug 2023 16:48:16 +0200 [thread overview]
Message-ID: <3d8ebdc7-8455-9ecb-ade0-30f47d028acf@mailbox.org> (raw)
In-Reply-To: <CALeDE9Pwy+DzrNrY6UWr=-MVEg-58yZoVnudBRDan-Bg+94StQ@mail.gmail.com>
On 8/8/23 16:31, Peter Robinson wrote:
> On Tue, Aug 8, 2023 at 3:27 PM Detlev Casanova
> <detlev.casanova@collabora.com> wrote:
>>
>> On Tuesday, August 8, 2023 10:21:11 A.M. EDT Peter Robinson wrote:
>>> On Thu, Jul 20, 2023 at 3:50 PM Detlev Casanova
>>>
>>> <detlev.casanova@collabora.com> wrote:
>>>> The command can be used to show various information that can be used to
>>>> identify the running system.
>>>>
>>>> Currently supported subcommands are:
>>>> * model: A string representing the model
>>>> * id: The id of the board
>>>> * revision: The revision of this board.
>>>
>>> How does this differ from the bdinfo and some of the other commands
>>> that provide similar info?
>>
>> If I'm not wrong, the bdinfo command is about showing what hardware is
>> present on the board. The sysinfo command is about showing board
>> identification information.
>
> Why can't bdinfo be extended rather than adding yet another command?
It could , but it feels like overloading bdinfo .
Sysinfo is system identification (i.e. stuff in eeprom), bdinfo is
things like memory layout.
prev parent reply other threads:[~2023-08-08 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 14:49 [PATCH v4 0/6] Introduce the sysinfo command Detlev Casanova
2023-07-20 14:49 ` [PATCH v4 1/6] sysinfo: Add IDs for board id and revision Detlev Casanova
2023-07-20 14:49 ` [PATCH v4 2/6] cmd: Add a sysinfo command Detlev Casanova
2023-07-20 14:49 ` [PATCH v4 3/6] sysinfo: Add a test Detlev Casanova
2023-07-20 14:49 ` [PATCH v4 4/6] sysinfo: Add documentation Detlev Casanova
2023-07-20 14:49 ` [PATCH v4 5/6] sysinfo: rcar3: Use int instead of char for revision Detlev Casanova
2023-07-20 14:49 ` [PATCH v4 6/6] sysinfo: rcar3: Implement BOARD_ID and BOARD_REV_* Detlev Casanova
2023-08-08 14:21 ` [PATCH v4 0/6] Introduce the sysinfo command Peter Robinson
2023-08-08 14:27 ` Detlev Casanova
2023-08-08 14:31 ` Peter Robinson
2023-08-08 14:48 ` Marek Vasut [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=3d8ebdc7-8455-9ecb-ade0-30f47d028acf@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=detlev.casanova@collabora.com \
--cc=hai.pham.ud@renesas.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=pbrobinson@gmail.com \
--cc=sjg@chromium.org \
--cc=tam.nguyen.xa@renesas.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