[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [alliance-iosk] Driver programming and GPL



Ramon van Handel wrote:

>
> >Well, want we *must* know is how to do a specific task, in case of floppy how
> >to read a sector, and generic management chores. Yes, ALL drivers code I know
> >of presumes to see all HW (i.e. ring 0).
>
> The VSTa drivers don't, which is why I recommend them to start with.

Ok, I'll give them a look.

> >I simply look the algorithm to access HW, and then change the interface to HW
> >itself. So, I now more or less know in which way manage floppy, I read ABL
> >code
> >and see how to do HW access inside Alliance and write that.
>
> The ABL code is not a good example of how HW access works in alliance.  It
> doesn't run under alliance, after all.  Please don't look at it if you want
> to learn that.

Yes, the boot code do whatever needed, so it's not the correct interfcace, though I
expect that in a way or another we don't duplicate drivers (/ABL and /LM?IOSK)
because it's a waste of resources and we don't have a lot of them.
But the real question is: which kind of interface I use? Can I use outp,inp, or
IOPL of  IOSK LMs forbid that? When I need an IRQ what I call? I'll need this
sooner or later....

Stefano

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