Subject: Re: NetBSD/pc98
To: None <email@example.com>
From: M. Warner Losh <firstname.lastname@example.org>
Date: 08/24/2006 16:20:06
In message: <email@example.com>
KIYOHARA Takashi <firstname.lastname@example.org> writes:
: > email@example.com wrote:
: > > I put sources and diff.
: > > ftp://ftp.netbsd.org/pub/NetBSD/misc/kiyohara/pc98/pc98-20060819.diff
: > > ftp://ftp.netbsd.org/pub/NetBSD/misc/kiyohara/pc98/pc98-20060819.tar.gz
: > - it looks a bit ugly to use flags of config(9) to denote
: > NE2000 variants in a config file.
: > Is there no way to probe them properly?
: > How FreeBSD/pc98 detects them?
: I don't know and there might not be means.
: IMHO can't support on ne(4) currently, because some boards do the map
: distorted. It is necessary the handlers as each registers. (like wdc(4))
Some of the cbus cards are ne2000 "compatible" while others of them
are wdc "compatible". The if_ed_cbus code to handle all of these
cases is somewhat complicated. It would be better if that driver had
a cleaner division like netbsd's.
: > - how will you handle symlinks in include dir on import?
: > which dir will machine@ symlink point? (no pc98/include/Makefile)
: They are provisional. I will copy from arch/i386/include. ;-)
FreeBSD/pc98 does this a little differently. We install i386/include
into /usr/include/i386 on pc98 machines. pc98/machine then typically
is just #include <i386/foo.h>. However, in the cases where there is a
difference, the file is more complicated.