From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BY8xv-00054P-1V for qemu-devel@nongnu.org; Wed, 09 Jun 2004 15:42:27 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BY8xq-00052S-8E for qemu-devel@nongnu.org; Wed, 09 Jun 2004 15:42:23 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BY8xp-00051s-QC for qemu-devel@nongnu.org; Wed, 09 Jun 2004 15:42:21 -0400 Received: from [193.252.22.26] (helo=mwinf0501.wanadoo.fr) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BY8wo-0002Ye-NL for qemu-devel@nongnu.org; Wed, 09 Jun 2004 15:41:18 -0400 Received: from bellard.org (ATuileries-112-1-3-149.w81-48.abo.wanadoo.fr [81.48.134.149]) by mwinf0501.wanadoo.fr (SMTP Server) with ESMTP id 4692A40046A for ; Wed, 9 Jun 2004 21:41:17 +0200 (CEST) Message-ID: <40C76872.9080507@bellard.org> Date: Wed, 09 Jun 2004 21:43:46 +0200 From: Fabrice Bellard MIME-Version: 1.0 Subject: Re: [Qemu-devel] NE2000 problem found References: <000701c44dfb$540106e0$0401a8c0@putte2k> In-Reply-To: <000701c44dfb$540106e0$0401a8c0@putte2k> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Mike Nordell wrote: > ne2000_asic_ioport_write: > if (s->dcfg & 0x01) { > /* 16 bit access */ > + assert(s->rcnt >= 2); > + assert(s->rsar + 2 <= s->stop); > ne2000_mem_writew(s, s->rsar, val); > s->rsar += 2; > s->rcnt -= 2; > } > > First assert triggered with: > s->dcfg: 0x49 > s->rcnt: 1 > s->rsar: 0x4156 > s->stop: 0xc000 > > What surprises me the most is that it's coming from an outb, not outw. Is > this really correct, or is the ne2000 emulation perhaps missing a > differentiation between 16- and 8-bit I/O? It is correct : the size of the transfer is determined by dcfg, not by the width of the I/O instruction. > I'll add *readb/writeb locally, to see if things go better, and report > findings/patch. Can you tell me exactly in which case you have problems with NE2000 ? BTW, did someone find why Windows XP has security problems in QEMU ? It seems related to the networking (the Safe mode without networking works, but not the one with networking), but I don't have enough knowledge of Windows to go further. Fabrice.