From: Stefan Weil <weil@mail.berlios.de>
To: sol10x86@cox.net, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [patch] More PCI ethernet emulations
Date: Wed, 28 Mar 2007 22:56:07 +0200 [thread overview]
Message-ID: <460AD667.8070608@mail.berlios.de> (raw)
In-Reply-To: <33328190.1174979798015.JavaMail.root@eastrmwml08.mgt.cox.net>
Good question. I stumbled about this, too, when I looked
at the code how I could apply your patch. Some months
had past since I wrote it :-)
The code writes to a serial EEPROM, so the 16 bits are
sent using only a clock and a single data bit. The
EEPROM emulation then takes the single bits and puts
them together.
The function gets a byte which contains clock, data and
two other significant bits, and 4 bits which are always 0.
When called with a word, only one byte is needed.
Maybe it is the wrong one - if you work with different
endianess.
I'l have a look at the other problems next weekend.
Stefan
Ben Taylor wrote:
> I have a question. in eepro100_write2, I see a word (16-bits) being
> passed in, but only the low part of the word gets written to the eeprom.
> Since it's a word write, shouldn't it be writing both bytes to the eeprom?
>
> Ben
next prev parent reply other threads:[~2007-03-28 20:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 7:16 [Qemu-devel] [patch] More PCI ethernet emulations Ben Taylor
2007-03-28 20:56 ` Stefan Weil [this message]
2007-04-02 12:32 ` Thiemo Seufer
[not found] ` <461FA372.6060105@mail.berlios.de>
[not found] ` <20070413163917.GB14303@networkno.de>
[not found] ` <461FBD8E.9010202@weilnetz.de>
[not found] ` <20070413182137.GC14303@networkno.de>
2007-09-24 17:54 ` [Qemu-devel] [Bug][Patch] Cirrus-VGA for Malta Stefan Weil
2007-09-24 21:12 ` Fabrice Bellard
2007-09-24 21:22 ` Fabrice Bellard
2007-09-25 11:28 ` Derek Fawcus
[not found] <23179021.1174880111656.JavaMail.root@eastrmwml08.mgt.cox.net>
2007-03-26 20:33 ` [Qemu-devel] [patch] More PCI ethernet emulations Stefan Weil
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=460AD667.8070608@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=qemu-devel@nongnu.org \
--cc=sol10x86@cox.net \
/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).