OSDev.org

Well, hello!:)

I re-started working on my OS, and currently it has outport's and inport's and printk, a way to access cmos values, itoa(), clrscr(), putchar.. My idea is to start having it support ext2fs mainly and networking. I am currently working on a kprintf.

I was thinking of figuring a way to have non-basic kernel features as somewhat modules. For example, I read that a good way to support multiple filesystems would be to use a virtual filesystem.

What can you recommend as a way to "organize" drivers, so that maybe in the future it could be easier to add other filesystems, or any drivers? And how can the kernel access/initialize them.

Thanks

My suggestion would be to read up on DOS' installable device drivers to get ideas. It is a rather simple interface which can be expanded upon rather easily. Go here -> http://www.freeinfosociety.com/computer ... nical.html for a reference starting point. Do a find on INSTALLABLE DEVICE DRIVERS. That section is filled with detailed information albeit based on DOS that you can use towards implementing your own style of device driver interface...ala 32-bit protected mode.

Cool, thanks!