> Shawn Leas <SLEAS@videoupdate.com> said:
> > From: Horst von Brand [mailto:vonbrand@inf.utfsm.cl]
> > >It stays in the source, developers have to take it into account,
> > >device drivers will have to be written both ways (devfs and not), ...
>
> > Wrong. The driver is written, and may or may not be adapted (with
> > only a few lines of code) to the device FS.
>
> It impacts all drivers then. Case closed.
>
Having _actually_ dealt with a non-devfs driver under devfs:
1. I had to make 0(zero)(NULL) changes for the driver to work
with devfs. None. Nada. Not a line, character, or bit.
2. Once devfs was installed I was able to make significant
behavioral changes with many fewer lines of code than
those changes would otherwise have taken. Less debugging,
cleaner result.
3. It wasn't until several weeks _after_ I had hacked all of
this that I noticed that there were special functions
available for devfs that would have let me do _more_!
-- Daniel Taylor Senior Test Engineer Digi International danielt@digi.com Open systems win.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/