qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Crosthwaite <peter.crosthwaite@petalogix.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: edgar.iglesias@gmail.com, qemu-devel@nongnu.org,
	john.williams@petalogix.com, paul@codesourcery.com
Subject: Re: [Qemu-devel] [RFC PATCH v1 2/4] m25p80: initial verion
Date: Tue, 5 Jun 2012 10:47:51 +1000	[thread overview]
Message-ID: <CAEgOgz66SrpBfaqWCE_6Sy=ajGvxErb4B=YL2oeyW3b-tu1Xjw@mail.gmail.com> (raw)
In-Reply-To: <4F7C445D.3070807@suse.de>

On Wed, Apr 4, 2012 at 10:53 PM, Andreas Färber <afaerber@suse.de> wrote:
> Am 30.03.2012 08:37, schrieb Peter A. G. Crosthwaite:
>> Added device model for m25p80 SPI flash
>>
>> Signed-off-by: Peter A. G. Crosthwaite <peter.crosthwaite@petalogix.com>
>> ---
>>  Makefile.target |    1 +
>>  hw/m25p80.c     |  495 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>  2 files changed, 496 insertions(+), 0 deletions(-)
>>  create mode 100644 hw/m25p80.c
>>
>> diff --git a/Makefile.target b/Makefile.target
>> index 8fd3718..fcccf1b 100644
>> --- a/Makefile.target
>> +++ b/Makefile.target
>> @@ -321,6 +321,7 @@ obj-microblaze-y = petalogix_s3adsp1800_mmu.o
>>  obj-microblaze-y += petalogix_ml605_mmu.o
>>  obj-microblaze-y += microblaze_boot.o
>>  obj-microblaze-y += spi.o
>> +obj-microblaze-y += m25p80.o
>>
>>  obj-microblaze-y += microblaze_pic_cpu.o
>>  obj-microblaze-y += xilinx_intc.o
>> diff --git a/hw/m25p80.c b/hw/m25p80.c
>> new file mode 100644
>> index 0000000..2b67375
>> --- /dev/null
>> +++ b/hw/m25p80.c
>> @@ -0,0 +1,495 @@
>> +/*
>> + * ST M25P80 emulator.
> [snip]
>
> A device by ST does not sound microblaze-specific and in that case,
> similar to the recent Atmel maxtouch device, should go into
> hw-obj-$(CONFIG_M25P80) instead so that it's compiled only once for
> microblaze-softmmu and microblazeel-softmmu.
>

Hi Andreas,

I have regenerated this series, but have not actioned this just yet. I
think adding a config switch is probably not the right solution, as
its just a device model. If every device model has a config switch
then isnt creating everyone config process going to be excessively
tedious? perhaps it can just live next to obj-y=ssi.o? I.E. if you
have SSI, then you have m25p80. I cant think of a case where you would
want SSI but need to exclude m25p80 from the build.

Regards,
Peter

> Same for spi.o since it implements a generic bus AFAIU.
>
> Andreas
>
> --
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2012-06-05  0:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30  6:37 [Qemu-devel] [RFC PATCH v1 0/4] SPI bus support + Xilinx SPI controller Peter A. G. Crosthwaite
2012-03-30  6:37 ` [Qemu-devel] [RFC PATCH v1 1/4] SPI: initial support Peter A. G. Crosthwaite
2012-03-30  7:37   ` Peter Maydell
2012-03-30  7:50     ` Peter Crosthwaite
2012-04-02 17:39   ` Peter Maydell
2012-04-02 23:51     ` Peter Crosthwaite
2012-04-03  0:48       ` Peter Crosthwaite
2012-04-03 17:45       ` Paul Brook
2012-04-03 18:08         ` Peter Maydell
2012-04-03 21:22           ` Paul Brook
2012-04-04  0:48             ` Peter Crosthwaite
2012-04-04 16:52               ` Paul Brook
2012-04-05  0:32                 ` Peter Crosthwaite
2012-04-05  7:18                   ` Peter Maydell
2012-04-02 23:57     ` Peter Crosthwaite
2012-04-03  0:27       ` Andreas Färber
2012-03-30  6:37 ` [Qemu-devel] [RFC PATCH v1 2/4] m25p80: initial verion Peter A. G. Crosthwaite
2012-04-03  7:03   ` Stefan Hajnoczi
2012-04-04 12:53   ` Andreas Färber
2012-06-05  0:47     ` Peter Crosthwaite [this message]
2012-06-05 12:38       ` Andreas Färber
2012-03-30  6:37 ` [Qemu-devel] [RFC PATCH v1 3/4] xilinx_spi: initial version Peter A. G. Crosthwaite
2012-03-30  6:37 ` [Qemu-devel] [RFC PATCH v1 4/4] petalogix-ml605: added spi controller with m25p80 Peter A. G. Crosthwaite

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='CAEgOgz66SrpBfaqWCE_6Sy=ajGvxErb4B=YL2oeyW3b-tu1Xjw@mail.gmail.com' \
    --to=peter.crosthwaite@petalogix.com \
    --cc=afaerber@suse.de \
    --cc=edgar.iglesias@gmail.com \
    --cc=john.williams@petalogix.com \
    --cc=paul@codesourcery.com \
    --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).