qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Setting up PPC440 Virtex Image for Qemu


From: Edgar E. Iglesias
Subject: Re: [Qemu-devel] Setting up PPC440 Virtex Image for Qemu
Date: Thu, 30 Jun 2011 14:32:24 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Thu, Jun 30, 2011 at 05:45:23PM +0530, Suzuki Poulose wrote:
> Hi,
> 
> I am working on enabling the KEXEC on PPC440 chipsets. To debug my patches,
> I would like to use the Qemu. The only available PPC440 support in Qemu is
> for the ppc-virtex. (Thanks for adding the support).
> 
> I was trying to use the default image provided at
> 
> http://wiki.qemu.org/download/ppc-virtexml507-linux-2_6_34.tgz
> 
> However I cannot get the network up for the board to use the nfs root file
> system.

Hi,

The problem is that there is no model of the LL-TEMAC in qemu, the one in
the refdesign beeing emulated. An easy way out is probably to connect
a xilinx,ethlite instead. You'll need to modify both QEMU and the dtb.

IIRC, the dtb published with the image has the lltemac removed.

I've got a working LL-temac model here, will try to post it this weekend.
Or if you're interested in hacking on it, I could probably code dump it as
is.


> ----
> PPC 4xx OCP EMAC driver, version 3.54
> TCP cubic registered
> NET: Registered protocol family 17
> VFS: Unable to mount root fs via NFS, trying floppy.
> VFS: Cannot open root device "nfs" or unknown-block(2,0)
> Please append a correct "root=" boot option; here are the available 
> partitions:
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
> ---
> 
> I tried using a different dtb based on virtex440-ml507.dts, but the
> qemu complains :
> 
> address@hidden ppc-virtex-ml507]$ ./qemu-run.sh
> Unable to copy device tree in memory
> 
> 
> Is there something I can do to get the networking up ? I think this may need 
> to
> be fixed in the dtb.
> 
>   Or is there any other mechanism to use a different file system ?
> ( I have the tool chain to build the kernel etc)


Another way is to create ramdisks with all the stuff you need and just
not use networking. Thats how the image from the wiki does it.

Cheers



reply via email to

[Prev in Thread] Current Thread [Next in Thread]