From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1DQlRV-0006Tl-0F
	for qemu-devel@nongnu.org; Wed, 27 Apr 2005 08:15:01 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1DQlRQ-0006Sb-Eu
	for qemu-devel@nongnu.org; Wed, 27 Apr 2005 08:14:59 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1DQlRQ-0006SW-9X
	for qemu-devel@nongnu.org; Wed, 27 Apr 2005 08:14:56 -0400
Received: from [211.5.2.83] (helo=nm01omta01f.dion.ne.jp)
	by monty-python.gnu.org with smtp (Exim 4.34) id 1DQlTC-00027g-Ha
	for qemu-devel@nongnu.org; Wed, 27 Apr 2005 08:16:46 -0400
Message-ID: <002201c54b23$da75a9d0$0364a8c0@afine>
From: "kazu" <kazoo@r3.dion.ne.jp>
References: <002301c54ad1$81217140$0364a8c0@afine>
	<426F2B36.70003@ntlworld.com>
Subject: Re: [Qemu-devel] NE2000 for OS/2
Date: Wed, 27 Apr 2005 21:23:00 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
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: qemu-devel@nongnu.org

Hi,

 Wednesday, April 27, 2005 3:03 PM Antony T Curtis wrote:

> kazu wrote:
>
> >Hi,
> >
> >A patch below supports NE2000 for a OS/2 Warp guest. The problem is that
PCI
> >bus isn't asserted when NE2000 is asserted. This patch is made by
lukewarm.
> >I heard that Realtek 8029 driver can be used in a OS/2 Warp guest.
> >
> >
> I have had some problems with using the RT8029 driver with OS/2 as
> guest. Personally, I prefer using the AMD PCNet-II driver and the only
> problems I have experienced with that is occasional SIGSEGV from the
> slirp code - no problems when I use the tap bridge.
>

Thanks. I wonder what's happened to slirp.

Regards,
kazu