Re: Driver for ADC 7841 Analogue Digital Converter

I've put this driver on my web page at : http://phaedra.apana.org.au/johna But, my original comments ommitted the fact that there is a data in pin, as well as a data out pin. The code itself is fine, and reflects this. The correct pin allocations are : port 0x278 bit 0, pin 2, Clock bit 1

Re: Driver for ADC 7841 Analogue Digital Converter

I've put this driver on my web page at : http://phaedra.apana.org.au/johna But, my original comments ommitted the fact that there is a data in pin, as well as a data out pin. The code itself is fine, and reflects this. The correct pin allocations are : port 0x278 bit 0, pin 2, Clock bit 1

Driver for ADC 7841 Analogue Digital Converter

I've put this driver on my web page at : http://phaedra.apana.org.au/johna This is not an attempt to do anything "official", merely point out that it's there so that anyone wanting to develop a driver for a serial type chip (or use that chip) has the option of a driver to start

Driver for ADC 7841 Analogue Digital Converter

I've put this driver on my web page at : http://phaedra.apana.org.au/johna This is not an attempt to do anything official, merely point out that it's there so that anyone wanting to develop a driver for a serial type chip (or use that chip) has the option of a driver to start with. I'm

nfs on a 2.4.0

I'm running linux-2.4.0-test9-pre7-riel on a 386 netstation, using etherboot and rootfs. Rootfs works fine. But ... Normally I mount /bin, /var, /etc, /lib (minimal) via rootfs, where they are required for booting, and operation of the box, and once booting has started, I mount /usr, /sbin and

nfs on a 2.4.0

I'm running linux-2.4.0-test9-pre7-riel on a 386 netstation, using etherboot and rootfs. Rootfs works fine. But ... Normally I mount /bin, /var, /etc, /lib (minimal) via rootfs, where they are required for booting, and operation of the box, and once booting has started, I mount /usr, /sbin and

Re: 2.4.0-test9 kernel problems

OK, yes the problem was a configuration one ... CONFIG_VT and CONFIG_VT_CONSOLE were set to y, but CONFIG_VGA_CONSOLE was set to n. It was this last one which was causing the problem. I now have the 386 kernel loading into the netstation, starting up, mounting rootfs, starting init and init

Re: 2.4.0-test9 kernel problems

OK, yes the problem was a configuration one ... CONFIG_VT and CONFIG_VT_CONSOLE were set to y, but CONFIG_VGA_CONSOLE was set to n. It was this last one which was causing the problem. I now have the 386 kernel loading into the netstation, starting up, mounting rootfs, starting init and init

2.4.0-test9 kernel problems (was 2.4 kernel problems on 386)

I had problems loading a variant of this kernel on a 386. The problems are now more obvious, as I've tried to operate this kernel, compiled for a 386, on my pentium pro. In this case, the kernel starts up, but has no communication with the screen. No messages are logged to the screen. However,

2.4.0-test9 kernel problems (was 2.4 kernel problems on 386)

I had problems loading a variant of this kernel on a 386. The problems are now more obvious, as I've tried to operate this kernel, compiled for a 386, on my pentium pro. In this case, the kernel starts up, but has no communication with the screen. No messages are logged to the screen. However,

Re: 2.4 kernel problems on 386

This was implied in my last email, but I thought I'd say it explicitly : I've had 2.0.36 and 2.2.15 kernels boot properly on the netstation - is it possible for whatever 386 stuff included in these kernels to become lost on the 2.2.4 kernel I've been using ? -- John August - To unsubscribe

2.4 kernel problems on 386

I'm trying to get a linux-2.4.0-test9-pre7 kernel with riel's recent memory swap patch going on a 386 - swapping problems with the 2.2.15 kernel I was using prompted this. I'm trying to make it run on a bull netstation, which means using bootp and etherboot tagged kernels. When I compile using

2.4 kernel problems on 386

I'm trying to get a linux-2.4.0-test9-pre7 kernel with riel's recent memory swap patch going on a 386 - swapping problems with the 2.2.15 kernel I was using prompted this. I'm trying to make it run on a bull netstation, which means using bootp and etherboot tagged kernels. When I compile using

Re: 2.4 kernel problems on 386

This was implied in my last email, but I thought I'd say it explicitly : I've had 2.0.36 and 2.2.15 kernels boot properly on the netstation - is it possible for whatever 386 stuff included in these kernels to become lost on the 2.2.4 kernel I've been using ? -- John August - To unsubscribe