Re: [alliance-iosk] Driver programming and GPL

[vhandel@chem.vu.nl (Ramon van Handel)]

>Ramon van Handel wrote:
>
>> Well, right now, all EKs have IO permissions.  But I don't want to keep it
>> that way.  As soon as CK security is implemented, I will turn this off -
>> that way, any user can load a new EK, but that EK cannot mess with the
>> hardware --> stable system.  When that is implemented, an EK that wants
>> hardware access needs to request I/O permissions from the CK.
>
>Fine, but you *should* spec this soon. Because otherwise a developer (as me:))
>cannot write drivers, and we need tons of that. On mine part, I'll write
>the LM for
>IOSK developer guide, when I'll start writing floppy driver.
>So, I propose you this:
>
>   CKsetIOPerm(baseaddr, length)  // incase of floppy base=0x3f0 length=8, if I
>remember well...

You can implement this in the EK libs as a 'shortcut'.

>> An EK that has the same capability as needed for I/O region allocation can
>> also request global interrupt forwarding.  In that case, the CK will send a
>> signal to that thread that requested it every time that interrupt (IRQ)
>> occurs.
>
>tell me how. Write some doc, and all we were happy. I know you don't like
>writing docs, but this one is essential info.

I love writing docs, but I love coding even more.  I will completely
document all of the CKs internals and externals in great detail in due
time.  For now, you example is demotasks.c - that's what it was made for
(well... partly ;)).  Read it, and all (?) will be clear.

Ramon


---
Ramon van Handel   <vhandel@chem.vu.nl>
Chemistry Student, OS Programmer and all-round Weirdo
The ant has made himself illustrious / Through constant industry industrious.
So what? Would you be calm and placid / If you were full of formic acid?
(Ogden Nash)


-
Alliance-IOSK:	http://iosk.allos.org/
Archive:	http://humbolt.nl.linux.org/lists/