1999.9.22
Now, I have Duo230 working with NetBSD-1.2.
I'm ready to work with it.
First, I'm plannig to make NetBSD-1.4.1 GENERIC kernel.

1999.9.24
/usr/sbin/config of NetBSD-1.2 seems to be different
from that of NetBSD-1.4.1.

1999.9.27
I made a newer /usr/sbin/config from the source in NetBSD-release.
Somehow, I need to remove -Werror from CFLAGS in the Makefile.

1999.9.29
There's a trouble with compiling /sys/compat/common/compat_exec.c.
Some Makefiles would be wrong?

1999.9.30
Re-making the /usr/bin/make of NetBSD-1.4.1 solves
the yesterday's problem.
But, building the kernel stops at the last step.
"ld" found unresolved symbols. Hmm..

1999.10.4
dt-1.1.7 was installed for a better environment.
But still stops at the last step.
Seems libkern.o does not have strcpy.o et al.

1999.10.5
/usr/share/mk was replaced by that of NetBSD-1.4.1
Would this help? Will try it later...

1999.10.6
In /sys/lib/libkern/Makefile,
somehow I need to modify "ARCHSUBDIR=m68k".
Now, I got a GENERIC kernel.
And, it did not boot. Oops!

1999.10.9
I re-compiled the kernel with -DDEBUG on and
some printf lines, and found it stops at get_pte().

1999.10.13
I changed all '.long 0xf0100800' in get_pte() in locore.s
to '.long 0xf0100c00' which mean to use the tt1 register
instead of the tt0 register. :-)
With this modified kernel, it boots and can see the prompt.
I can't use the keyboard, though.
I will try making kernel with ADB_DEBUG on.

1999.10.14
I also need to add 'adb_debug = 1' for ADB_DEBUG working.
The kernel seems to find 0 targets for ADB Device. Hmm.

1999.10.17
There's a still trouble with ADB recognition.
The codes around ADBs are different from those in NetBSD-1.2.

1999.10.20
I moved the line
"adb_setup_hw_type();    /* setup hardware type */"
in adb_direct.c (adb_reinit())
before the line
"if (adbHardware != ADB_HW_PB)".
Nothing changed.
Is pm_direct.c working?

1999.10.24
I've commentted out the line
"if ((via_reg(VIA1, vIFR) & 0x10) == 0x10)"
in pm_direct.c (inside pm_adb_op()).
It seems too easy, but the kernel find 2 ADB targets
and I can use the keyboard. (I can get the prompt.)

1999.10.27
Inside check_video() in machdep.c,
the line
"if(!get_physical(videoaddr,&phys))"
is replaced by the line
"phys=videoaddr;if(0)"
and it makes me to use "dt".
(You might run "X".)

1999.10.28
DUOTEST kernel is now available.

1999.11.1
Now, I'm installing NetBSD-1.4.1.

1999.11.3
NetBSD-1.4.1 has been installed.
Failed to build kernel with signal 4.
Some FPE could be wrong?

1999.11.4
I'm re-installing NetBSD-1.2 again...

1999.11.8
NetBSD-1.2 was installed.
Making DUOTEST kernel is in progress.

1999.11.9
Getting -current kernel of 1999.11.8.
Some Makefile does not seem to work fine with NetBSD-1.2.

1999.11.16
Still hard to compile -curent kernel.
gcc of NetBSD-1.2 is too old?

1999.11.17
FPE code was replaced by that of 1.4.
I made a new 1.4.1-based DUOTEST kernel.
And installed 1.4.1 binary sets.
The new kernel seems to work fine.

1999.11.18
Newer gas was compiled for builing -current kernel.

1999.11.28
Still having trouble with -current kernel.
newer FPE code does not seem to work fully.

2000.1.18
Have FPE problems solved? I do not know.
I havn't tried it very much.
Currently, my interest is a support for NetDock
-- an ethernet adapter for Duo-series.
BUT, there seems to be no document about NetDock.
What can I do?

2000.2.1
Is it possible to access .ENET driver from NetBSD?
Currently not, but I hope so.

2000.3.8
There was no .ENET driver but .ENET0 driver.
.ENET0 driver in the declaration ROM is too Mac specific,
and it seems to be impossible to access from NetBSD.
I am in progress reading .ENET0 code in the ROM.

2000.3.30
I'm just trying writing an Asante NetDock driver
from the ROM driver code.
Little knowledge abount network drivers and assembler language
makes me very hard to do it.

2000.4.18
Asante NetDock driver works only limitted functions.
It does not seem to complete transmittion.
Debugging drivers is really hard for me.

2000.5.8
NetDock driver works fine now.
Although it's a little bit slow.
Almost done with my Duo support. Yeah!