[Buildroot] [PATCH v3] manual: add QEMU demo to quick start

Ciro Santilli ciro.santilli at gmail.com
Wed Oct 10 12:26:17 UTC 2018


On Wed, Oct 10, 2018 at 1:14 PM Thomas Petazzoni
<thomas.petazzoni at bootlin.com> wrote:
>
> Hello,
>
> On Wed, 10 Oct 2018 10:18:12 +0100, Ciro Santilli wrote:
> > Signed-off-by: Ciro Santilli <ciro.santilli at gmail.com>
> > ---
> > OK, I think this is the best way to structure the more general intro to
> > configs and their docs.
>
> It seems like you haven't taken into account my previous comment.
>

Sorry, which one did I miss?

In any case, if you think kind of intro might be useful, can you make
the adjustment that you have in mind and it yourself? I think it would
be easier in this case. No need to credit me or anything.

I just highly recommend keeping:

+make qemu_x86_64_defconfig
+make BR2_JLEVEL="$(nproc)"
+qemu-system-x86_64 \
+  -M pc \
+  -kernel output/images/bzImage \
+  -drive file=output/images/rootfs.ext2,if=virtio,format=raw \
+  -append "root=/dev/vda" \
+  -net nic,model=virtio \
+  -net user

as close as possible to the top of the getting started ;-)

> > +=== Try it out with QEMU
> >
> > -From the buildroot directory, run
> > +If you just want to emulate a simple generic QEMU system to see
> > +Buildroot in action immediately, run from the buildroot directory:
> > +
> > +--------------------
> > +make qemu_x86_64_defconfig
> > +make BR2_JLEVEL="$(nproc)"
> > +qemu-system-x86_64 \
> > +  -M pc \
> > +  -kernel output/images/bzImage \
> > +  -drive file=output/images/rootfs.ext2,if=virtio,format=raw \
> > +  -append "root=/dev/vda" \
> > +  -net nic,model=virtio \
> > +  -net user
> > +--------------------
>
> Please point the user to board/qemu/x86-64/readme.txt instead,
> don't duplicate the information. And I believe the section should be
> made more general, and talk about all defconfigs. Maybe a section:
>
> "Quick start on HW platforms or Qemu"
>
> and then describe that we have defconfigs, how to use them, that we
> have readme files to explain how to use the result of the defconfigs,
> etc.
>
>
> > +=== Day-to-day workflow
> > +
> > +In your day-to-day workflow, the first step when using Buildroot is to
> > +create a custom configuration.
> > +
> > +If you wish to use an existing configuration as your starting point,
> > +first find the available configs with:
> > +
> > +--------------------
> > + $ ls configs/
> > +--------------------
> > +
> > +If you want to build for the Raspberry Pi 3 for example, run:
> > +
> > +--------------------
> > + $ make raspberrypi3_64_defconfig
> > +--------------------
> > +
> > +This command generates a +.config+ file in the root directory.
> > +
> > +Each defconfig is documented under:
> > +
> > +--------------------
> > + $ board/<config-hyphenated>/readme.txt
> > +--------------------
> > +
> > +for example:
> > +
> > +--------------------
> > + $ less board/raspberrypi3-64/readme.txt
> > +--------------------
> > +
> > +Next, to customize the +.config+, Buildroot has a nice configuration tool
> > +similar to the one you can find in the http://www.kernel.org/[Linux kernel]
> > +or in http://www.busybox.net/[BusyBox]. Run it either with
>
> I am not sure this section "Day-to-day workflow" is very useful/makes a
> lot of sense in the context of the Buildroot manual.
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com



More information about the buildroot mailing list