From: Palmer Dabbelt <palmer@dabbelt.com>
To: akira.tsukamoto@gmail.com
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-riscv@lists.infradead.org
Subject: Re: Linux 5.14-rc2
Date: Mon, 09 Aug 2021 09:19:37 -0700 (PDT) [thread overview]
Message-ID: <mhng-cf5d58bf-52d0-4342-92f4-f94e40450840@palmerdabbelt-glaptop> (raw)
In-Reply-To: <bba05067-6f2f-6166-02a0-839f514d3780@gmail.com>
On Sun, 25 Jul 2021 02:56:51 PDT (-0700), akira.tsukamoto@gmail.com wrote:
> On 7/24/21 09:58, Palmer Dabbelt wrote:
>>> I have sent the fixes yesterday in my time.
>>>
>>> https://lists.infradead.org/pipermail/linux-riscv/2021-July/007621.html
>>>
>>> Guenter and Geert have confirmed the fix.
>>>
>>> https://lists.infradead.org/pipermail/linux-riscv/2021-July/007634.html
>>> https://lists.infradead.org/pipermail/linux-riscv/2021-July/007626.html
>>>
>>> Akira
>>
>> Thanks. I've got these on fixes now, I'll send them up tomorrow morning assuming the autobuilders don't find any issues. Like I said in the other thread I wasn't getting these allmodconfig failures, so if there's an easy way to reproduce them I'd be happy to add it to my setup -- I don't really know anything about GCC plugins, I'm just using Debian's toolchain for my Linux test setup (haven't gotten around to merging it with my GCC test setup, and it's been a decade so I guess I should stop pretending that's going to happen ;)).
>
> Sure, my procedure is based on Guenter’s instructions.
> I built qemu v6.0.0, buildroot 2021.05 and the kernel with the toochain came with buildroot.
>
> # qemu
> git clone https://gitlab.com/qemu-project/qemu.git
> cd qemu
> git checkout -b v6.0.0
> git submodule update --init --recursive
> git submodule sync --recursive
> ./configure --target-list=riscv32-softmmu --disable-user --disable-gnutls --disable-docs --disable-nettle --disable-gcrypt --disable-vnc-png --disable-xen --disable-xen-pci-passthrough --disable-libssh
> make -j $(nproc)
>
> # buildroot
> git clone git://git.buildroot.net/buildroot
> cd buildroot/
> git checkout 2021.05 -b 2021.05
> make qemu_riscv32_virt_defconfig
> make
>
> # kernel
> export PATH=locaion_of_buildroot/output/host/bin:${PATH}"
> Built kernel.
>
> # prepare booting rv32
> Downloaded rootfs.cpio and run.sh from Guenter’s link to inside buildroot/output/images/.
> http://server.roeck-us.net/qemu/riscv32/
>
> cd output/images
> Used revised run.sh.
> ```
> export PATH="location_of_qemu/build:${PATH}"
> export KERNEL_DIR=location_of_kernel/arch/riscv/boot/
> qemu-system-riscv32 -M virt -m 512M -no-reboot \
> -bios default -kernel ${KERNEL_DIR}Image \
> -initrd rootfs.cpio \
> -append "rdinit=/sbin/init console=ttyS0,115200 earlycon=uart8250,mmio,0x10000000,115200" \
> -nographic -monitor none
> ```
>
> The rootfs.cpio checks the network after booting and poweroff immediately to return to shell.
Thanks. I was actaully asking for the randstruct build instructions,
but Geert already provided those in the other thread. Given how easy
the 32-bit boot is now, though, I figured I'd just get it up and
running. It's in now.
Thanks!
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2021-08-09 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHk-=wjYghA5O+ZsWKVNApMK3j4V1EibO5P+c4MrHnqp8YhY=g@mail.gmail.com>
[not found] ` <20210719140437.GA2178213@roeck-us.net>
2021-07-20 17:24 ` Linux 5.14-rc2 Linus Torvalds
2021-07-20 17:27 ` Linus Torvalds
2021-07-21 0:26 ` Akira Tsukamoto
2021-07-24 0:58 ` Palmer Dabbelt
2021-07-25 9:56 ` Akira Tsukamoto
2021-08-09 16:19 ` Palmer Dabbelt [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=mhng-cf5d58bf-52d0-4342-92f4-f94e40450840@palmerdabbelt-glaptop \
--to=palmer@dabbelt.com \
--cc=akira.tsukamoto@gmail.com \
--cc=linux-riscv@lists.infradead.org \
--cc=torvalds@linux-foundation.org \
/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).