From: Stefan Weil <weil@mail.berlios.de>
To: "Sébastien BRICE" <seb@so-sweet.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] eepro100: feature is missing in this emulation: unknown word write
Date: Wed, 23 Mar 2011 00:06:28 +0100 [thread overview]
Message-ID: <4D892B74.7040408@mail.berlios.de> (raw)
In-Reply-To: <AANLkTikW2E+FYngFsO0NTFCHoC=C=aFgBieCNecmcgvA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3507 bytes --]
Am 22.03.2011 22:03, schrieb Sébastien BRICE:
> Le 21 mars 2011 22:48, Alex Williamson <alex.williamson@redhat.com
> <mailto:alex.williamson@redhat.com>> a écrit :
>
> 2011/3/21 Sébastien BRICE <seb@so-sweet.org
> <mailto:seb@so-sweet.org>>:
> > Hi everyone
> >
> > I have been using qemu-kvm with success the last two years and
> its really
> > amazing.
> > I am new to this mailing list and i am requesting your
> assistance because i
> > struggle to have my virtual card working with an 'exotic'
> virtual System
> >
> > seb@debian:~/qemu-kvm-0.14.0$ kvm -net nic,model=i82557b
> /media/prologue.img
> >
> >
> > Whatever i try the guest system never initializes the Intel 100
> Pro NIC Card
> > as it is supposed to do
> >
> > And thats almost working with eep100.c source and -net
> nic,model=i82557b
> > option
> > But each time the qemu hangs with:
> >
> > eepro100: feature is missing in this emulation: unknown word write
> ...
> > default:
> > logout("addr=%s val=0x%04x\n", regname(addr), val);
> > missing("unknown word write");
> > }
> > }
>
> Can you set DEBUG_EEPRO100 in the source file, rebuild and let us know
> what extra debug output you get? Just change the #if 0 around the
> define near the top of the file to #if 1.
>
> Alex
>
>
> Thx you Alex
> Here is what i have with DEBUG_EEPRO100 set in the eepro100.c source file
>
> seb@debian:~/qemu_building/
> qemu-kvm-0.14.0$ x86_64-softmmu/qemu-system-x86_64 -n
> nic,model=i82557b prologue.img
>
> /EE100 e100_nic_init
> EE100 e100_pci_reset 0x2b5ba10
> EE100 e100_nic_init macaddr: 52 54 00 12 34 56
> EE100 nic_reset 0x2b5ba10
> EE100 nic_selective_reset checksum=0xfd33
> EE100 e100_nic_init model=i82557b,macaddr=52:54:00:12:34:56
> Warning: vlan 0 is not connected to host network
> EE100 nic_reset 0x2b5ba10
> EE100 nic_selective_reset checksum=0xfd33
> EE100 pci_mmio_map region 0, addr=0xf2020000,
> size=0x00001000, type=8
> EE100 pci_map region 1, addr=0x0000c040,
> size=0x00000040, type=1
> EE100 pci_mmio_map region 2, addr=0xf2040000,
> size=0x00020000, type=0
> EE100 eepro100_write2 addr=Port+0 val=0x0000
> EE100 eepro100_write2 addr=Port+0 val=0x0000
> eepro100: feature is missing in this emulation: unknown word write
> EE100 eepro100_write2 addr=Port+2 val=0x0000
> EE100 eepro100_write2 addr=Port+2 val=0x0000
> eepro100: feature is missing in this emulation: unknown word write
> EE100 eepro100_write2 addr=Port+0 val=0x1d01
> EE100 eepro100_write2 addr=Port+0 val=0x1d01
> eepro100: feature is missing in this emulation: unknown word write
> EE100 eepro100_write2 addr=Port+2 val=0x07ff
> EE100 eepro100_write2 addr=Port+2 val=0x07ff
> /
> its not crystal clear for me, do you have any clue to get this working
> a bit better ?
> thank you for your advices
>
> Seb
The current emulation only supports 32 bit writes to the "port" address.
I'll read the documentation to see how 16 bit writes should be handled
(obviously your image always writes lower and upper half of the 32 bit
value, and for this case, the solution might be simple).
Is prologue.img available online (so I can run your test scenario)?
Regards,
Stefan W.
[-- Attachment #2: Type: text/html, Size: 4675 bytes --]
prev parent reply other threads:[~2011-03-22 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 21:03 [Qemu-devel] eepro100: feature is missing in this emulation: unknown word write Sébastien BRICE
2011-03-22 23:06 ` Stefan Weil [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=4D892B74.7040408@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=qemu-devel@nongnu.org \
--cc=seb@so-sweet.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).