Yes, there is a good reason why the NE2k emulation was disabled in
plex86--debugging. We decided to focus in on just getting plex86 to work
before we started messing with the way that it accesses devices. Now
that we are going to be able to start working more on devices (in the near
future anyway...) it is reasonable to assume that work on the NE2k
emulation may resume.
On Wed, 30 May 2001, Martin wrote:
> I know that plex 86 used to support basic emulation of a ne2000 network
> card (this was originally developed for bochs).
> I found out that in the recent CVS version this is disabled (configure
> option --enable-ne2000 is removed)
> I hacked the support back in only to find out there is only support for
> freebsd host.
> The freebsd version uses a bpf packet filter device /dev/bpf000
> On linux there is also standard support for packet filtering so this
> could be made to work on linux too.
We also discussed using the routing code built into the kernel and the raw
network support devices availble to the system. We are trying to make a
system which will be extensible to many operating systems (the BSD's,
LINUX, W9x, WinNT...., etc.) so we must be careful not to trip ourselves
up.
> My questions:
> Is there a special reason why the ne2000 code was removed in plex86?
> Is reimplementing and improving this code and making versions of this
> for all host-OSes the way to go or should we make a fresh start?
>
> the ne2000 support can be found in plex86/user/plugins/bochs/iodev
> eth.cc
> eth.h
> eth_fbsd.cc The freebsd implementation
> eth_null.cc This is an empty framework for implementing on other
> hosts as freebsd
> ne2k.cc
> ne2k.h
> The code can be re-enabled by adding all eth and ne2k .o objects to
> BX_HW_IODEV_OBJS in the iodev Makefile (can be done nicely by changing
> config.h.in, configure.in and iodev/Makefile.in)
>
> Greetings,
> Martin DvH
>
Drew Northup, N1XIM
