From: Stefan Weil <weil@mail.berlios.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH 6/9] eepro100: Support compilation without EEPROM
Date: Tue, 06 Apr 2010 16:26:42 +0200 [thread overview]
Message-ID: <4BBB44A2.8020508@mail.berlios.de> (raw)
In-Reply-To: <20100406121017.GD16539@redhat.com>
Michael S. Tsirkin schrieb:
> On Tue, Apr 06, 2010 at 01:44:06PM +0200, Stefan Weil wrote:
>
>> To emulate hardware without an EEPROM,
>> EEPROM_SIZE may be set to 0.
>>
>> Signed-off-by: Stefan Weil <weil@mail.berlios.de>
>> ---
>> hw/eepro100.c | 2 ++
>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>
>> diff --git a/hw/eepro100.c b/hw/eepro100.c
>> index cedc427..e12ee23 100644
>> --- a/hw/eepro100.c
>> +++ b/hw/eepro100.c
>> @@ -1866,9 +1866,11 @@ static int e100_nic_init(PCIDevice *pci_dev)
>>
>> e100_pci_reset(s, e100_device);
>>
>> +#if EEPROM_SIZE > 0
>> /* Add 64 * 2 EEPROM. i82557 and i82558 support a 64 word EEPROM,
>> * i82559 and later support 64 or 256 word EEPROM. */
>> s->eeprom = eeprom93xx_new(EEPROM_SIZE);
>> +#endif
>>
>
> I expect long-term EEPROM_SIZE will stop being a compile-time
> constant then?
>
>
EEPROM_SIZE might be a qdev parameter, so a new eeprom_size
would become part of the device status.
Up to now, there was no need for it.
>>
>> /* Handler for memory-mapped I/O */
>> s->mmio_index =
>> --
>> 1.7.0
>>
next prev parent reply other threads:[~2010-04-06 14:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 11:44 [Qemu-devel] eepro100: New patches Stefan Weil
2010-04-06 11:44 ` [Qemu-devel] [PATCH 1/9] eepro100: Don't allow writing SCBStatus Stefan Weil
2010-04-06 11:44 ` [Qemu-devel] [PATCH 2/9] eepro100: Simplify status handling Stefan Weil
2010-04-06 12:18 ` [Qemu-devel] " Michael S. Tsirkin
2010-04-06 14:29 ` Stefan Weil
2010-04-06 14:34 ` Michael S. Tsirkin
2010-04-06 11:44 ` [Qemu-devel] [PATCH 3/9] eepro100: Simplified device instantiation Stefan Weil
2010-04-06 11:44 ` [Qemu-devel] [PATCH 4/9] eepro100: Add new device variant i82801 Stefan Weil
2010-04-06 11:44 ` [Qemu-devel] [PATCH 5/9] eepro100: Set configuration bit for standard TCB Stefan Weil
2010-04-06 11:44 ` [Qemu-devel] [PATCH 6/9] eepro100: Support compilation without EEPROM Stefan Weil
2010-04-06 12:10 ` [Qemu-devel] " Michael S. Tsirkin
2010-04-06 14:26 ` Stefan Weil [this message]
2010-04-06 15:44 ` [Qemu-devel] " Richard Henderson
2010-04-06 16:01 ` Stefan Weil
2010-04-06 16:35 ` Richard Henderson
2010-04-07 1:00 ` Paul Brook
2010-04-07 7:02 ` Stefan Weil
2010-04-07 7:29 ` Michael S. Tsirkin
2010-04-06 11:44 ` [Qemu-devel] [PATCH 7/9] eepro100: Set power management capability using pci_reserve_capability Stefan Weil
2010-04-06 12:09 ` [Qemu-devel] " Michael S. Tsirkin
2010-04-06 11:44 ` [Qemu-devel] [PATCH 8/9] eepro100: Fix mapping of flash memory Stefan Weil
2010-04-06 11:57 ` [Qemu-devel] " Michael S. Tsirkin
2010-04-06 14:23 ` Stefan Weil
2010-04-06 14:30 ` Michael S. Tsirkin
2010-04-06 11:44 ` [Qemu-devel] [PATCH 9/9] eepro100: Fix PCI interrupt pin configuration regression Stefan Weil
2010-04-06 11:55 ` [Qemu-devel] " Michael S. Tsirkin
2010-04-06 12:40 ` [Qemu-devel] Re: eepro100: New patches Michael S. Tsirkin
2010-04-06 16:09 ` Stefan Weil
2010-04-07 8:10 ` Michael S. Tsirkin
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=4BBB44A2.8020508@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=mst@redhat.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).