Control: tag -1 moreinfo
On Sat, 2018-09-08 at 20:07 +0200, Karsten Merker wrote:
> On Thu, Sep 06, 2018 at 10:28:19PM +0100, Ben Hutchings wrote:
> > On Thu, 2018-09-06 at 22:06 +0200, Karsten Merker wrote:
> > > Source: linux
> > > Version: 4.19~rc2-1~exp1
> > > Severity: wishlist
>
> [...]
> > > starting with version 4.19rc2, the mainline Linux kernel includes
> > > all drivers necessary for running a riscv64 system in qemu, so it
> > > would be great if the "linux" source package could be extended to
> > > build a linux-image-*-riscv64 binary package.
> > >
> > > Attached is a patch that tries to add the necessary bits.
> >
> > This config sets a whole lot of things to be built-in, but our policy
> > is to build everything as modules if it works properly work as a
> > module. This will also cause the building of installer udebs to fail
> > (empty packages are treated as a fatal error).
>
> Hello,
>
> the reason for using a static config was that using an initrd
> isn't possible on riscv64 with kernel 4.19rc2. This will
> hopefully change sometime before the final 4.19 release so that
> we can move to a fully modularized config, but for now everyting
> required to mount the rootfs and bring up init has to be
> built-in. I can probably trim down the current static config a
> bit more, but e.g. filesystem drivers need to be built-in for
> now, otherwise mounting the rootfs isn't possible.
[...]
This is not OK for distribution kernel packages. The addition of riscv
will have to wait until it has support for an initramfs.
Is this commit sufficient to make booting with an initramfs work:
commit cdc7274029ca5984350a057a2399aaa340d3be2d
Author: Guenter Roeck <linux@roeck-us.net>
Date: Tue Aug 28 17:33:46 2018 -0700
riscv: Do not overwrite initrd_start and initrd_end
or are more changes needed?
Ben.
--
Ben Hutchings
Who are all these weirdos? - David Bowie, on joining IRC
Attachment:
signature.asc
Description: This is a digitally signed message part