> > you can just build your own kernel and use it instead. > > Jacques has a kernel config file that can be used as a > > template. I have to build my own, since I could not get > > the IDE driver to work properly. > > > So the ide driver is not compiled into the kernel and you > couldn't load something like ide.o in initrd.lrp?
Since we don't use modprobe, the ide modules: ide-mod.o ide-mod-probe.o, ide-disk.o, ... have to be loaded at the right sequence. I did it and get it to work with my kernel, but not Jacques' one. I did not pursue any further once I got it to work. > > The only tricky part is to rebuild the initrd image: initrd.lrp, > > to include the mtd device drivers. > > Is there an mtd.o? There is no mtd.o, but a collection of mtd drivers: mtd-core.o, docecc.o, doc2000.o, docprobe.o, and nftl.o, to support DOC2000. > Is that the only .o module that needs to be loaded specially for > the DOC, assuming the ide support is compiled into the kernel? You don't need ide support to be built-in into the kernel. I have been playing with two systems: one with DOC2000 and one with a small IDE disk. On the DOC2000 system, I don't need ide at all. Again, the problem is that we don't use modprobe. The mtd or ide drivers have to be loaded in the right sequence for them to detect the hardware and work properly. Since they are required during bootup, they have to be loaded from the initrd image. Bao _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
