Page 5 of 5
Re:
Posted: Fri Aug 07, 2009 10:10 am
by kokjo
cyr1x wrote:
3. Create a new (or extend) executable format for drivers, where the identifier is stored. (The hardest solution and harder to make it portable)
no. thats maybe the easy'est. make a section in an elf file with a name like : .driver_or_something_like_that
you cot do that in nasm:
like:
Code: Select all
section .text
code:
bla bla...
section .driver
db 'this the driver section!',0
Re: Extensible Driver Interface
Posted: Thu Oct 03, 2013 6:54 am
by bellezzasolo
Yep, that would be portable, a section. PE and ELF support it. Might be an idea to have a backup though (like a string ID'd struct).
It does need enumeration. Also perhaps an EXTENSIBLE Bus implementation (I.E. Bus drivers can be plugged in with their own info slot).
Of course, to be portable you cannot use OO (which would be really nice for a driver if done properly (CDriver->CKybrdDriver->CPS2KybrdDriver))
This looks like a nice project.
Re: Extensible Driver Interface
Posted: Thu Oct 03, 2013 7:16 am
by Combuster
Of course, to be portable you cannot use OO
Necromancing for the purpose of posting nonsense?
