> Now I am completely ignorant of how the fbcon stuff works in the
> latest kernels, but one of the things that we will need in order to
> support this is the ability access the file system so we can
> dynamically load our Nucleus drivers from disk. The code to load the
> drives simply relies upon standard C file I/O functions (which may
> not be available in the kernel, but some sort of file I/O must be?)
> and is pure, portable C code so that can compile for the kernel just
> fine. However when does the fbcon stuff get initialised, and can it
> be initialised late enough in the bootup sequence such that the
> device drivers for the console can be loaded from the file system?
> What sort of problems are we going to have to face getting our driver
> loading code working in the kernel?
Trying to load anything directly from the kernel code is not the
right way to go. The best solution would be probably to make everything
standard kernel modules and send requests for loading of modules to
the kmod daemon -- see the request_module() function.
Have a nice fortnight
-- Martin `MJ' Mares <mj@ucw.cz> http://atrey.karlin.mff.cuni.cz/~mj/ Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth "You have new nail."- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html