From: "Mike Nordell" <tamlin@algonet.se>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: NE2000 problem found
Date: Thu, 10 Jun 2004 04:43:57 +0200 [thread overview]
Message-ID: <000a01c44e94$c844b990$0401a8c0@putte2k> (raw)
I have now seen some pretty convincing evidence that ASIC byte-writes
*shall* be honoured, and disregard the 8/16-bit mode as specified by (dcfg &
1).
Guest: Windows 2000 sp4.
While in 16-bit mode (dcfg & 1):
- It sets EN0_RCNTLO to an odd value.
- Writes everything as 16-bit values (outw) except for the last byte.
- Writes the last byte using outb, which triggers the interrupt.
So there should be a separate ne2000_asic_ioport_writeb.
I also have good reasons to believe there should not be a matching readb
function. As a test I did implement such a function, but then I got a MAC of
52-52-54-54-00-00 :-)
/Mike
next reply other threads:[~2004-06-10 2:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 2:43 Mike Nordell [this message]
2004-06-10 5:10 ` [Qemu-devel] IDE issues?? (Was re: NE2000 problem found) Tim
-- strict thread matches above, loose matches on Subject: below --
2004-06-10 5:21 [Qemu-devel] Re: NE2000 problem found Mike Nordell
2004-06-17 4:50 ` Leigh Dyer
2004-06-26 5:06 ` kazu
2004-06-09 21:58 Mike Nordell
2004-06-09 23:17 ` Fabrice Bellard
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='000a01c44e94$c844b990$0401a8c0@putte2k' \
--to=tamlin@algonet.se \
--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).