From: Leon Alrae <leon.alrae@imgtec.com>
To: Leon Alrae <leon.alrae@imgtec.com>, qemu-devel@nongnu.org
Cc: yongbok.kim@imgtec.com, cristian.cuna@imgtec.com,
paul.burton@imgtec.com, aurelien@aurel32.net
Subject: Re: [Qemu-devel] [PATCH 0/6] mips_malta: fixes to support YAMON firmware
Date: Fri, 28 Jun 2013 14:20:58 +0100 [thread overview]
Message-ID: <51CD8DBA.10408@imgtec.com> (raw)
In-Reply-To: <1371195048-19618-1-git-send-email-leon.alrae@imgtec.com>
ping
http://patchwork.ozlabs.org/patch/251250/
http://patchwork.ozlabs.org/patch/251254/
http://patchwork.ozlabs.org/patch/251253/
http://patchwork.ozlabs.org/patch/251251/
http://patchwork.ozlabs.org/patch/251252/
http://patchwork.ozlabs.org/patch/251249/
On 14/06/13 08:30, Leon Alrae wrote:
> From: Paul Burton <paul.burton@imgtec.com>
>
> This patchset fixes some bugs with MIPS malta emulation allowing the YAMON
> firmware to run.
>
> YAMON can be found at http://www.mips.com/products/system-software/yamon/
>
> You can then boot to a YAMON prompt by passing the path to yamon-XX.bin to
> the -bios argument or by writing yamon-XX.bin to the start of a flash image
> passed to the -pflash argument. The YAMON 2.21 release & newer have been tested
> to work.
>
> There is still a bug preventing YAMON from initialising the ethernet controller
> so an application or kernel cannot be loaded via TFTP. However the serial
> console functions and can examine or modify memory, modify the flash and
> environment variables, access disks etc.
>
> As of YAMON 2.22 a YAMON bug prevents the environment from being initialized
> correctly by an "erase -e" command if you begin with a zeroed flash image. As
> a workaround you can fill empty areas of your flash image with 1s be generating
> your flash image like so:
>
> dd if=/dev/zero bs=1M count=4 | tr '\0' '\377' >flash.bin
> dd if=yamon-02.22.bin of=flash.bin conv=notrunc
>
> Paul Burton (6):
> mips_malta: fix BIOS endianness swapping
> mips_malta: correct reading MIPS revision at 0x1fc00010
> mips_malta: generate SPD EEPROM data at runtime
> mips_malta: cap BIOS endian swap length at 0x3e0000 bytes
> mips_malta: generate SMBUS EEPROM data
> pflash_cfi01: duplicate status byte from bits 23:16 for 32bit reads
>
> hw/block/pflash_cfi01.c | 3 +
> hw/mips/mips_malta.c | 219 +++++++++++++++++++++++++++++++++++------------
> 2 files changed, 166 insertions(+), 56 deletions(-)
>
next prev parent reply other threads:[~2013-06-28 13:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 7:30 [Qemu-devel] [PATCH 0/6] mips_malta: fixes to support YAMON firmware Leon Alrae
2013-06-14 7:30 ` [Qemu-devel] [PATCH 1/6] mips_malta: fix BIOS endianness swapping Leon Alrae
2013-06-14 7:30 ` [Qemu-devel] [PATCH 2/6] mips_malta: correct reading MIPS revision at 0x1fc00010 Leon Alrae
2013-07-29 4:33 ` Andreas Färber
2013-06-14 7:30 ` [Qemu-devel] [PATCH 3/6] mips_malta: generate SPD EEPROM data at runtime Leon Alrae
2013-06-14 7:30 ` [Qemu-devel] [PATCH 4/6] mips_malta: cap BIOS endian swap length at 0x3e0000 bytes Leon Alrae
2013-06-14 7:30 ` [Qemu-devel] [PATCH 5/6] mips_malta: generate SMBUS EEPROM data Leon Alrae
2013-06-14 7:30 ` [Qemu-devel] [PATCH 6/6] pflash_cfi01: duplicate status byte from bits 23:16 for 32bit reads Leon Alrae
2013-06-28 13:20 ` Leon Alrae [this message]
2013-07-18 7:34 ` [Qemu-devel] [PATCH 0/6] mips_malta: fixes to support YAMON firmware Leon Alrae
2013-07-28 22:24 ` Aurelien Jarno
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=51CD8DBA.10408@imgtec.com \
--to=leon.alrae@imgtec.com \
--cc=aurelien@aurel32.net \
--cc=cristian.cuna@imgtec.com \
--cc=paul.burton@imgtec.com \
--cc=qemu-devel@nongnu.org \
--cc=yongbok.kim@imgtec.com \
/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).