New device filesystems

[James S. <jsi...@tr...>]

As some might have noticed we are starting work on devices filesystems.
For those that don't know what this is about look at the 

LANANA: To Pending Device Number 

thread on the kernel mailing list. We basically are build filesystems for
each type of device. This allows us to have more than one file represent a
device instead of the traditional UNIX method of one file to one device.
As you can image this gives much more power to the driver writer. 
   One advantage to such a design is network transprancy. You can program
devices remotely. This means for example on embedded devices, even a cell
phone, you could have a kernel image a just NFS some machine remotely. On
that remote machine you could program the hardware on the cell phone.
   Another advantage is you could write basic scripts to preform hardware
functions. For example we could do a 

echo "640x480-16@70" > /dev/gfx/card0/mode1



P.S

   A few commits about the code entered into CVS. I really like to create
a directory devfs2 and place gfxfs in their. The reason is I like to write
the inputfs as well. Plus in time we probable will add more device
classes like sound to this directory. I just like to keep the fs directory
clean.
   The second thing is you have 

struct file_operations gfxfs_file_ops = {
        mmap:           generic_file_mmap,
        llseek:         generic_file_llseek,
};

For this filesystem to be truly network transparent we also need to remove
mmap support as well as ioctl support. Read and write only.