All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
	YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] is there any value in a short section somewhere on H/W bringup tools?
Date: Tue, 25 Nov 2025 15:47:26 +0000	[thread overview]
Message-ID: <90133708303aa9fdb7d2bc0cbe3c70aabfc3f3a0.camel@linuxfoundation.org> (raw)
In-Reply-To: <8f9e9bb5-e84e-c9a2-bd27-105ffae5c2e8@crashcourse.ca>

On Tue, 2025-11-25 at 06:35 -0800, Robert P. J. Day wrote:
> 
>   Is there any value in adding a short section on useful OE-available
> hardware bringup utilities? i just added this to an image to help me
> poke around a new board:
> 
>   IMAGE_INSTALL:append = " \
>         devmem2 \
>         dtc \
>         ethtool \
>         i2c-tools \
>         libgpiod \
>         libubootenv-bin \
>         lshw \
>         mdio-tools \
>         phytool \
>         spitools \
>         usbutils \
>   "
> 
> might this be something that would be appropriate for the BSP guide,
> or as a section in the dev tasks manual? (i'm sure there are other
> packages that would belong here as well.)

Most of these are in meta-openembedded? If so, would a packagegroup
there make sense?

Cheers,

Richard

  reply	other threads:[~2025-11-25 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25 14:36 is there any value in a short section somewhere on H/W bringup tools? Robert P. J. Day
2025-11-25 15:47 ` Richard Purdie [this message]
2025-11-25 15:53   ` [docs] " Robert P. J. Day

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=90133708303aa9fdb7d2bc0cbe3c70aabfc3f3a0.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=rpjday@crashcourse.ca \
    /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.