DiskonChip problems.
I used to have DiskonChip stuff working on 2.4.18 kernel, but I've been forced to upgrade to 2.4.31 and now I can't get it to work.
I used to have a driver called fldrvlnx, which created a module called doc.o and I'd simply load that module and then I could mount the DiskonChip with a line in fstab like
/dev/fla1 /mnt/fla1 msdos defaults 0 0
Now I see in 2.4.31, things have moved on and the DiskonChip stuff is different. Can someone enlighten me as to how I'm supposed to get it to work ?
Thanks
Quoted 5 lines · On Tue, 2005-09-06 at 18:39 +0000, [email protected] wrote:
I used to have a driver called fldrvlnx, which created a module called doc.o and I'd simply load that module and then I could mount the DiskonChip with a line in fstab like
/dev/fla1/mnt/fla1msdos defaults 0 0
You were using a binary-only module. If you were shipping embedded products which used a combination of that and the GPL'd kernel, then you were violating the GPL. You really shouldn't admit to such things in public. I hope you were doing this only in your lab and not shipping such code.
Quoted 3 lines
Now I see in 2.4.31, things have moved on and the DiskonChip stuff is different. Can someone enlighten me as to how I'm supposed to get it to work ?
Enable the DOC2000 hardware driver and NFTL, and it should turn up as /dev/nftla
Signature · 1 line
dwmw2
Quoted 5 lines · David Woodhouse
You were using a binary-only module. If you were shipping embedded products which used a combination of that and the GPL'd kernel, then you were violating the GPL. You really shouldn't admit to such things in public. I hope you were doing this only in your lab and not shipping such code.
OK. I'm well aware of the GPL. I'm was not shipping anything. I was just trying to prove to myself that the DOC (and hardware interface) did work.
Anyway, thanks to your help I'm now using the kernel and modules exclusively.
Thanks again.
Mike