qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "François Revol" <revol@free.fr>
To: salvatorelionetti@yahoo.it, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PowerPC] New board walnut with u-boot
Date: Fri, 14 Nov 2008 00:36:17 +0100 CET	[thread overview]
Message-ID: <16356729852-BeMail@laptop> (raw)
In-Reply-To: <588538.91101.qm@web27207.mail.ukl.yahoo.com>

Hi,

> i've ported u-boot-1.1.6 and DHT walnut board to qemu-0.9.1
> environment.
> At qemu side:
> - LACK of flash CFI interaction, i2c, PCI support,
> - CONTAIN board parameter, serial, emac full support

Oh, interesting.
I want to port Haiku to the SAM440 board, which uses PPC, but also U-
Boot (couldn't they just use OF ?), so I'll need to add U-Boot support
to Haiku, so I really welcome this to be able to test it :)

http://www.sam440.com/eng/summerfollies.html

Btw, 1.1.6 seems quite old for U-Boot...
Do you plan on porting the current one too ?
I will need some features that are still being worked on (the external
API, to use U-Boot as kind of minimal BIOS, to let our bootloader use
it to send serial debug and do disk/other I/O before the kernel is
loaded).

> To integrate the patch, and simplify integration, i need some info
> - is the current trunk in use svn://svn.sv.gnu.org/qemu/trunk?

Yes.
patches, and developments in general should be made against trunk, else
you'll have to keep up merging your patches from the old version which
wastes both your and the devs time.

> - could i directly deliver such work?

Just post the diff on this list, you'll get comments about them, and
maybe commits if they are ok.

François.

  parent reply	other threads:[~2008-11-13 23:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13 22:27 [Qemu-devel] [PowerPC] New board walnut with u-boot Salvatore Lionetti
2008-11-13 23:03 ` Jean-Christophe PLAGNIOL-VILLARD
2008-11-13 23:36 ` François Revol [this message]
2008-11-14  0:43   ` Salvatore Lionetti

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=16356729852-BeMail@laptop \
    --to=revol@free.fr \
    --cc=qemu-devel@nongnu.org \
    --cc=salvatorelionetti@yahoo.it \
    /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).