From: Avi Kivity <avi@redhat.com>
To: Kay Ackermann <kay.ackermann@uni-ulm.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] e1000 fix: read access to some registers is missing.
Date: Sun, 01 Nov 2009 16:05:32 +0200 [thread overview]
Message-ID: <4AED95AC.8030900@redhat.com> (raw)
In-Reply-To: <172731552.20091031182943@uni-ulm.de>
On 10/31/2009 07:29 PM, Kay Ackermann wrote:
>
> While writing working on an e1000 driver for my university's OS I
>
> noticed that some registers aren't readable in QEMU, but they should
>
> be readable as stated in Intels Driver Developer Manual (and also
>
> verified on real hardware).
>
>
>
> diff --git a/hw/e1000.c b/hw/e1000.c
>
> index 028afd1..3987e70 100644
>
> --- a/hw/e1000.c
>
> +++ b/hw/e1000.c
>
> @@ -789,6 +789,8 @@ static uint32_t (*macreg_readops[])(E1000State *,
> int) = {
>
> getreg(MANC), getreg(MDIC), getreg(SWSM),
> getreg(STATUS),
>
> getreg(TORL), getreg(TOTL), getreg(IMS),
> getreg(TCTL),
>
> getreg(RDH), getreg(RDT), getreg(VET),
> getreg(ICS),
>
> + getreg(TDBAL), getreg(TDBAH), getreg(RDBAH),
> getreg(RDBAL),
>
> + getreg(TDLEN), getreg(RDLEN),
>
> [TOTH] = mac_read_clr8, [TORH] = mac_read_clr8,
> [GPRC] = mac_read_clr4,
>
> [GPTC] = mac_read_clr4, [TPR] = mac_read_clr4,
> [TPT] = mac_read_clr4,
>
>
>
>
> Oh and is there any specific reason why Jumbo-Frames are limited to 4k
> instead of i.e. Alteon 9014 bytes?
>
>
>
There used to be a 4K buffer somewhere in the path. I think it's larger
now.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-11-01 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 17:29 [Qemu-devel] [PATCH] e1000 fix: read access to some registers is missing Kay Ackermann
2009-11-01 14:05 ` Avi Kivity [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=4AED95AC.8030900@redhat.com \
--to=avi@redhat.com \
--cc=kay.ackermann@uni-ulm.de \
--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).