hello kitohara-san

In message: <20060822.014148.70203456.kiyohara@kk.iij4u.or.jp>
            KIYOHARA Takashi <kiyohara@kk.iij4u.or.jp> writes:
: > kiyohara@kk.iij4u.or.jp 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. 
: 
:   http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pc98/conf/GENERIC.hints?rev=1.26&content-type=text/x-cvsweb-markup
: 
:   e.g.
:     hint.ed.5.flags="0x600000"
:     hint.ed.1.flags="0x200000"
: 
: 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.

Warner