[haiku-development] Re: Is the "poke" driver supposed to be private?

  • From: Christian Packmann <Christian.Packmann@xxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Wed, 18 Feb 2009 11:34:28 +0100

François Revol schrieb:
I guess there will be no easy way to directly do hardware accesses anymore, and that any application which requires this will need to install its own driver(s), correct?

Well, we'll probably have to use it to implement the pseudo-standard linux io funcs or some other. For now it's not a problem but later those shall be restricted to root only at least.

Yes, that would be good. The easy hardware access in BeOS really was a gaping security hole.

Anyway, "applications" should never access hardware directly, that's what drivers are for. The only acceptable reason would be driver prototyping.

Well, I used the low-level access with DeskbarSensor and was in a continuous driver prototyping phase, trying to support hardware monitoring chips I'd never run on. Cheap solution, but it worked... but I'm kinda glad that I have to rewrite this in a better way for Haiku.

btw, please fix your MUA to wrap lines.

Thanks for the hint, done.

Christian

Other related posts: