From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Meswj-0006bM-SC
	for qemu-devel@nongnu.org; Sat, 22 Aug 2009 11:56:01 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Meswe-0006U3-QO
	for qemu-devel@nongnu.org; Sat, 22 Aug 2009 11:56:01 -0400
Received: from [199.232.76.173] (port=36486 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Meswe-0006To-KB
	for qemu-devel@nongnu.org; Sat, 22 Aug 2009 11:55:56 -0400
Received: from mail.gmx.net ([213.165.64.20]:59437)
	by monty-python.gnu.org with smtp (Exim 4.60)
	(envelope-from <Reimar.Doeffinger@gmx.de>) id 1Meswd-0005ji-Vm
	for qemu-devel@nongnu.org; Sat, 22 Aug 2009 11:55:56 -0400
Date: Sat, 22 Aug 2009 17:55:52 +0200
From: Reimar =?iso-8859-1?Q?D=F6ffinger?= <Reimar.Doeffinger@gmx.de>
Subject: Re: [Qemu-devel] eepro100c additions/changes required for VxWorks
	5.4.2 to work
Message-ID: <20090822155552.GA9800@1und1.de>
References: <0A54BACCF270364FBD51EAC504A0F0670F8880EA@FRMRSSXCHMBSC2.dc-m.alcatel-lucent.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <0A54BACCF270364FBD51EAC504A0F0670F8880EA@FRMRSSXCHMBSC2.dc-m.alcatel-lucent.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "ZAPPACOSTA, Rolando (Rolando)" <zappacosta@alcatel-lucent.com>
Cc: qemu-devel@nongnu.org

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...