From: "Sebastian Herbszt" <herbszt@gmx.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ne2k_isa: how to specify a custom iobase and irq?
Date: Fri, 18 Dec 2009 22:16:34 +0100 [thread overview]
Message-ID: <37C6733CEA434E0A96FA20ED780D28ED@FSCPC> (raw)
In-Reply-To: <4B2BEC96.7040508@codemonkey.ws>
Anthony Liguori wrote:
> Sebastian Herbszt wrote:
>> Markus Armbruster wrote:
>>> "Sebastian Herbszt" <herbszt@gmx.de> writes:
>>>
>>>> The default iobase and irq for the ne2k_isa card are 0x300 and 9.
>>>> It should be possible to override both using the "-net" syntax like
>>>> "-net nic,model=ne2k_isa,irq=5,iobase=0x280".
>>>
>>> -device ne2k_isa,irq=5,iobase=0x280
>>
>> If i specify "-net nic,model=pcnet" i end up only with a pcnet nic. With
>> the above syntax i get a e1000 and a ne2k_isa. It also loads the e1000
>> rom.
>
> Can you supply the full command lines. I'm a little confused about what
> you're reporting.
"qemu -device ne2k_isa,irq=10" and "info qtree" has e1000 and ne2k_isa.
"qemu -net nic,model=pcnet" and "info qtree" has only pcnet.
Maybe because of hw/pc.c:
if (!pci_enabled || (nd->model && strcmp(nd->model, "ne2k_isa") == 0))
pc_init_ne2k_isa(nd);
else
pci_nic_init_nofail(nd, "e1000", NULL);
- Sebastian
next prev parent reply other threads:[~2009-12-18 21:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 21:29 [Qemu-devel] ne2k_isa: how to specify a custom iobase and irq? Sebastian Herbszt
2009-12-18 6:12 ` Markus Armbruster
2009-12-18 8:37 ` Gerd Hoffmann
2009-12-18 20:00 ` Sebastian Herbszt
2009-12-18 20:54 ` Anthony Liguori
2009-12-18 21:43 ` Sebastian Herbszt
2009-12-18 23:23 ` Anthony Liguori
2009-12-18 19:58 ` Sebastian Herbszt
2009-12-18 20:56 ` Anthony Liguori
2009-12-18 20:24 ` Sebastian Herbszt
2009-12-18 20:56 ` Anthony Liguori
2009-12-18 21:16 ` Sebastian Herbszt [this message]
2009-12-21 12:37 ` Markus Armbruster
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=37C6733CEA434E0A96FA20ED780D28ED@FSCPC \
--to=herbszt@gmx.de \
--cc=anthony@codemonkey.ws \
--cc=armbru@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).