From: Andreas Ziegler <br015@umbiko.net>
To: ct clmsn <ct.clmsn@gmail.com>
Cc: Buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] kernel install from buildroot
Date: Sat, 19 Apr 2025 15:26:25 +0000 [thread overview]
Message-ID: <6c0f8202ef17cd38940edb4e518a218d@umbiko.net> (raw)
In-Reply-To: <mailman.3.1745064001.375107.buildroot@buildroot.org>
Hi ct,
On 2025-04-18 16:03, ct clmsn wrote:
>
> Hello,
>
> This should be a pretty trivial question mostly asking to make sure my
> assumptions are correct.
>
> I'm doing hardware testing with an SBC. I have an SBC that is
> configured to
> boot from an NVME-SSD. A vendor encouraged me to use buildroot to
> compile a
> new kernel. My preference would be to just update the existing
> environment
> on my SBC's NVME-SSD.
>
> Given `buildroot/output/target` contains the compiled linux kernel with
> firmware, which directories or files should I be concerned with copying
> over on the NVME-SSD?
Buildroot copies the final kernel image to output/images. In addition
you need the content of output/target/lib/modules.
Kind regards,
Andreas
> Thanks in advance for the assistance and confirming my
> back-of-the-envelope
> verification.
>
> v/r,
> ct
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next parent reply other threads:[~2025-04-19 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3.1745064001.375107.buildroot@buildroot.org>
2025-04-19 15:26 ` Andreas Ziegler [this message]
[not found] ` <CAN4Cwatp=c58JzpGD3SZS8692m0TtYd879jON2B7D_vn=PqJcA@mail.gmail.com>
2025-04-23 5:15 ` [Buildroot] kernel install from buildroot Andreas Ziegler
2025-04-23 12:06 ` ct clmsn
2025-04-18 20:03 ct clmsn
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=6c0f8202ef17cd38940edb4e518a218d@umbiko.net \
--to=br015@umbiko.net \
--cc=buildroot@buildroot.org \
--cc=ct.clmsn@gmail.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