Quoting ming deng <[EMAIL PROTECTED]>: > >Some device drivers (video, audio, network etc.) may need to plug into > >kernel structures to be useful. But many devices (like digital cameras and > >MP3 players) can and are supported by userspace apps. > > Can you tell me why drivers for video, audio and network can not be built > into user space applications?
You can do that if, for example, this application is all you ever run on this system. This can be true for some embedded systems. A scanner application, for example, can be made to access certain device, read from it and produce output. This is all fine and good. However if you want the device to be shared, or use a high level interface (soundcore, V4L, SCSI...) then you would need to channel the data back into the kernel, into appropriate subsystems - and that is not a good thing to do. So yes, you can make an app with its own Ethernet interface. Only don't expect the TCP/IP stack to service this device... you have to do everything in your app. Dmitri
msg02471/pgp00000.pgp
Description: PGP signature
