linux-openrisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Ann Yun <by.ann.yun@gmail.com>
Cc: jonas@southpole.se, stefan.kristiansson@saunalahti.fi,
	corbet@lwn.net, linux-openrisc@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation:openrisc: Add build instructions with initramfs
Date: Sat, 26 Apr 2025 09:50:43 +0100	[thread overview]
Message-ID: <aAyeY-cFSDuLYnJZ@antec> (raw)
In-Reply-To: <20250425201018.12756-1-by.ann.yun@gmail.com>

On Fri, Apr 25, 2025 at 04:10:18PM -0400, Ann Yun wrote:
> Mention how to include initramfs when building the kernel
> 
> Signed-off-by: Ann Yun <by.ann.yun@gmail.com>
> ---
>  Documentation/arch/openrisc/openrisc_port.rst | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/Documentation/arch/openrisc/openrisc_port.rst b/Documentation/arch/openrisc/openrisc_port.rst
> index a8f307a3b499..4ab28879d7ed 100644
> --- a/Documentation/arch/openrisc/openrisc_port.rst
> +++ b/Documentation/arch/openrisc/openrisc_port.rst
> @@ -40,6 +40,10 @@ Build the Linux kernel as usual::
>  	make ARCH=openrisc CROSS_COMPILE="or1k-linux-" defconfig
>  	make ARCH=openrisc CROSS_COMPILE="or1k-linux-"
>  
> +If you want to embed initramfs in the kernel, also pass ``CONFIG_INITRAMFS_SOURCE``. For example::
> +
> +	make ARCH=openrisc CROSS_COMPILE="or1k-linux-" CONFIG_INITRAMFS_SOURCE="path/to/rootfs path/to/devnodes"
> +

I think this is good, but maybe we can mention to refer to Documentation/filesystems/ramfs-rootfs-initramfs.rst
for more details on this?

Also, it may be helpful to mention we can get pre-built busybox rootfs images
here:

  https://github.com/stffrdhrn/or1k-rootfs-build/releases

But if we do that then it would be better to show how to use thos rootfs images,
which maybe something better we have in our openrisc/tutorials[0].

-Stafford

[0] https://github.com/openrisc/tutorials

>  3) Running on FPGA (optional)
>  
>  The OpenRISC community typically uses FuseSoC to manage building and programming
> -- 
> 2.37.2
> 

  reply	other threads:[~2025-04-26  8:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-25 20:10 [PATCH] Documentation:openrisc: Add build instructions with initramfs Ann Yun
2025-04-26  8:50 ` Stafford Horne [this message]
2025-04-26 13:58   ` Ann Yun

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=aAyeY-cFSDuLYnJZ@antec \
    --to=shorne@gmail.com \
    --cc=by.ann.yun@gmail.com \
    --cc=corbet@lwn.net \
    --cc=jonas@southpole.se \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-openrisc@vger.kernel.org \
    --cc=stefan.kristiansson@saunalahti.fi \
    /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;
as well as URLs for NNTP newsgroup(s).