[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150525132930.GR13811@NP-P-BURTON>
Date: Mon, 25 May 2015 14:29:30 +0100
From: Paul Burton <paul.burton@...tec.com>
To: Rob Landley <rob@...dley.net>
CC: <linux-mips@...ux-mips.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
"Jiri Slaby" <jslaby@...e.cz>, Paolo Bonzini <pbonzini@...hat.com>,
Leonid Yegoshin <Leonid.Yegoshin@...tec.com>,
Kernel Mailing List <linux-kernel@...r.kernel.org>,
James Hogan <james.hogan@...tec.com>,
"Steven J. Hill" <Steven.Hill@...tec.com>,
Hannes Reinecke <hare@...e.de>,
Andrew Bresticker <abrestic@...omium.org>,
Thomas Gleixner <tglx@...utronix.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Ralf Baechle" <ralf@...ux-mips.org>,
Qais Yousef <qais.yousef@...tec.com>,
<linux-serial@...r.kernel.org>,
Markos Chandras <markos.chandras@...tec.com>,
Christoph Hellwig <hch@....de>, Michal Marek <mmarek@...e.cz>,
Jason Cooper <jason@...edaemon.net>,
"David S. Miller" <davem@...emloft.net>,
"Bart Van Assche" <bvanassche@....org>,
Jeffrey Deans <jeffrey.deans@...tec.com>,
"David Daney" <david.daney@...ium.com>
Subject: Re: [PATCH 00/15] MIPS Malta DT Conversion
On Mon, May 25, 2015 at 02:59:31AM -0500, Rob Landley wrote:
> On Fri, May 22, 2015 at 10:50 AM, Paul Burton <paul.burton@...tec.com> wrote:
> > This series begins converting the MIPS Malta board to use device tree,
> > which is done with a few goals in mind:
> >
> > - To modernise the Malta board support, providing a cleaner example to
> > people referencing it when bringing up new boards and reducing the
> > amount of code they need to write.
> >
> > - To make the code at the board level more generic with the eventual
> > aim of sharing it between multiple boards & allowing for
> > multi-platform kernel binaries. Although this series doesn't result
> > in the kernel reaching those goals, it is a step in that direction.
> >
> > - To result in a more maintainable kernel through a combination of the
> > above.
>
> How would I go about testing this under qemu?
>
> (Especially the "more than 256 megs ram" part. :)
Hi Rob,
With the series applied you can start from malta_defconfig, enable
CONFIG_HIGHMEM, build your kernel then run QEMU like so:
$ qemu-system-mipsel -kernel vmlinux -m 1G -append memsize=1G -serial stdio
If you apply this patch to QEMU:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg297902.html
(or if you use a real board) then you can omit the memsize argument from
the kernel command line (ie. the -append) and just do:
$ qemu-system-mipsel -kernel vmlinux -m 1G -serial stdio
The kernel will then retrieve the correct memory size from the
bootloader-provided environment and make use of all the available RAM.
Thanks,
Paul
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists