qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javier@dowhile0.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org,
	linaro-toolchain <linaro-toolchain@lists.linaro.org>
Subject: Re: [Qemu-devel] [PATCH 1/1] hw: Add IGEPv2 board support
Date: Wed, 11 Jan 2012 13:58:55 +0100	[thread overview]
Message-ID: <CABxcv=mndgjL20T83S==6b9cedWQX5ir96L2B+WitJgS307Peg@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA8+xf0dJdJ7-wYVkhNjZ3pz8_eg1P-QMxrCmsrpoT4JdA@mail.gmail.com>

On Wed, Jan 11, 2012 at 1:20 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 11 January 2012 11:53, Javier Martinez Canillas <javier@dowhile0.org> wrote:
>> Yes, the IGEPv2 and the Overo are indeed very similar machines so we
>> base the hardware modeling on the Overo.
>>
>> The only differences here are which OMAP version is used to initialize
>> the MPU (3630 instead of 3430) and the NAND memory used, Numonyx
>> OneNAND instead of Micron NAND.
>
> That's pretty minor -- can you just use the overo model as is?
> I bet nothing at the software level cares that much about the
> OMAP version or NAND manufacturer...
>

Yes, I guess we can use the Overo as is.

>> We just add this device model for our clients so I thought it was a
>> good idea to post the patch upstream. But feel free to ignore me if
>> you think that it doesn't add any value to Linaro QEMU.
>
> I appreciate the patch. My pushback is really that every new board
> we accept carries an implicit future cost for testing/maintenance/etc,
> so there needs to be a reasonable set of users who would use this
> and not the overo or beagle.
>

Yes, I totally understand. Then just feel free to just ignore the
patch, sorry for the noise.

>> Sorry about that, I didn't know that GPLv2 or later was the norm in
>> the QEMU project.
>
> We've just changed recently to asking people to include the "or later"
> clause for new code (this is why, as you note, there are some existing
> bits of code which are v2-only).
>
> -- PMM

Best regards,
Javier

      reply	other threads:[~2012-01-11 12:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11  8:43 [Qemu-devel] [PATCH 1/1] hw: Add IGEPv2 board support Javier Martinez Canillas
2012-01-11 11:15 ` Peter Maydell
2012-01-11 11:53   ` Javier Martinez Canillas
2012-01-11 12:20     ` Peter Maydell
2012-01-11 12:58       ` Javier Martinez Canillas [this message]

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='CABxcv=mndgjL20T83S==6b9cedWQX5ir96L2B+WitJgS307Peg@mail.gmail.com' \
    --to=javier@dowhile0.org \
    --cc=linaro-toolchain@lists.linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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).