[openbeos] Re: Kernel status (POSIX)

>Outside of the bounds of posix, where are the IVTs defined
>and documented for NewOS/BeOS?

OK, that is more clear.

>If I'm writing a BeOS driver I don't really care much about
>posix, I care where the OS hooks are for the hardware
>and the kernel interface.

Really, you still shouldn't care. That is really something for the PCI and
ISA bus managers to handle. Driver authors just need to supply functions
that get called on interrupt. 

As you probably suspect, this is not documented, yet. Still, that should
not hold up anyone's progress.

>Thank god!
>I hope the north and south bridge code is also a module.
>It would be nice to be able to generate drivers for the various
>chipsets and plug them in, instead of getting locked into something
>that's hard coded into the kernel.

I can't think of much that is in the bridge chips, other than, maybe
some initialization stuff, that you couldn't replace in BeOS.

>Alright!, ATA133 here we come!
>ATAPI/SCSI-3 HERE WE COME!!!!!

I am hoping that we will have ATA133 out of the box.
AFA scsi, that is just a kernel add-on. Same as BeOS.

>I feel all tingley.  :)
>
>Peter
>
>
>




Other related posts: