From: "Reimar Döffinger" <Reimar.Doeffinger@gmx.de>
To: "ZAPPACOSTA, Rolando (Rolando)" <zappacosta@alcatel-lucent.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] eepro100c additions/changes required for VxWorks 5.4.2 to work
Date: Sat, 22 Aug 2009 17:55:52 +0200 [thread overview]
Message-ID: <20090822155552.GA9800@1und1.de> (raw)
In-Reply-To: <0A54BACCF270364FBD51EAC504A0F0670F8880EA@FRMRSSXCHMBSC2.dc-m.alcatel-lucent.com>
On Wed, Aug 19, 2009 at 11:38:21AM +0200, ZAPPACOSTA, Rolando (Rolando) wrote:
> I was able to make VxWorks 5.4.2 load from FTP it's target binary file (I'll now try to figure out why I receive some VxWorks errors once it finishes the download).
>
> To do so, I had to implement some 8255x features not yet included as well as to change some of the already coded ones.
Some of your changes are basically "cosmetic", e.g. replacing a single assert by
if+message+assert(0), could you please point out which parts are really
necessary?
Btw. I already some time ago sent a patch that implements CmdDiagnose (also sets
status to 0), which is also necessary for OpenSolaris (which also needs RX_ABORT
support in addition).
I find it hard to imagine that the reads you implemented are necessary, since they
would be unaligned which I for some reason believe aren't allowed and/or in
real hardware get split by the PCI implementation or something...
next prev parent reply other threads:[~2009-08-22 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 9:38 [Qemu-devel] eepro100c additions/changes required for VxWorks 5.4.2 to work ZAPPACOSTA, Rolando (Rolando)
2009-08-22 15:55 ` Reimar Döffinger [this message]
2009-08-22 16:42 ` ZAPPACOSTA, Rolando (Rolando)
2009-08-22 20:09 ` Reimar Döffinger
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=20090822155552.GA9800@1und1.de \
--to=reimar.doeffinger@gmx.de \
--cc=qemu-devel@nongnu.org \
--cc=zappacosta@alcatel-lucent.com \
/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).