[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [alliance-iosk] Driver programming and GPL
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...
> 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.
Stefano
-
Alliance-IOSK: http://iosk.allos.org/
Archive: http://humbolt.nl.linux.org/lists/