I have some questions about the user-kernel interface of the me4000 driver. From my looking through the code it seems specific to the me4000 hardware which does concern me since there are hundreds of different data acquisition devices from many different vendors. In my opinion it would beneficial if at the very least all of these devices shared a common device interface. Additionally there is the out of tree Comedi project: http://comedi.org Which supports this hardware, and many more, with a generic device interface. There may be other reason not to merge Comedi (I know they have a desire to maintain support of their RT support), but I can't help but feel that merging the me4000 driver without thinking about the hundreds of other devices out there is a mistake. -- Shawn --
| Jens Axboe | Re: [BUG] New Kernel Bugs |
| KAMEZAWA Hiroyuki | Re: 2.6.24-rc3-mm1 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Jarek Poplawski | Re: [BUG #12364] Re: HTB - very bad precision? HFSC works fine! 2.6.28 |
| Alexey Dobriyan | Re: [GIT]: Networking |
