...thanx for the replies anyway:) as soon as I compiled the code into the kernel, rather than running it as a module, open() and close() worked fine... the hardware is a propriatery image scanner, used by the company I work for in their gaming terminals, so licenses are not a problem:) the firmware is now loaded as a file, which the kernel reads in before starting init()... anyhow, I think a paper on how to make your module a part of the kernel source tree (with corresponding options in make *config and the Makefiles) is something that needs writing... if no-one has done it before I get more time on my hands, the author might even be me *s*
well, maybe not really, but the Amigas back in 1985 had hardware collision detection. They did it by having the graphics chip checking for overlaps between the "background (odd bitplanes)", the "foreground(even bitplanes)" and the 4 sprite-pairs. If a collision was detected, an interrupt was generated.
Slashdot Mirror
...thanx for the replies anyway :) as soon as I compiled the code into the kernel, rather than running it as a module, open() and close() worked fine ... the hardware is a propriatery image scanner, used by the company I work for in their gaming terminals, so licenses are not a problem :) the firmware is now loaded as a file, which the kernel reads in before starting init() ... anyhow, I think a paper on how to make your module a part of the kernel source tree (with corresponding options in make *config and the Makefiles) is something that needs writing ... if no-one has done it before I get more time on my hands, the author might even be me *s*
well, maybe not really, but the Amigas back in 1985 had hardware collision detection. They did it by having the graphics chip checking for overlaps between the "background (odd bitplanes)", the "foreground(even bitplanes)" and the 4 sprite-pairs. If a collision was detected, an interrupt was generated.