[patch 2/5] Staging: vme: add VME userspace driver
Emilio G. Cota
cota at braap.org
Tue Aug 11 07:04:08 UTC 2009
Greg KH wrote:
> On Mon, Aug 10, 2009 at 10:05:26PM +0200, Emilio G. Cota wrote:
> > Greg KH wrote:
> > > On Sun, Aug 09, 2009 at 02:17:16PM +0200, Emilio G. Cota wrote:
> > > > > Instead of using that we implemented a heretic IOCTL-based
> > > > > interface for user-space; at least with it you could create a
> > > > > driver (with no interrupt support) for a device in user-space.
> > >
> > > Why not just use the UIO interface instead of creating
> > > yet-another-kernel/user-api?
> > >
> > > Will that interface not work for what you want to use here?
> > Certainly. I didn't mean we'd like to see that merged. Currently
> > we make extensive use of IOCTLs because we are maintaining
> > kernel and user-space code for two platforms/OSes (ppc-lynx and
> > x86-linux), and not having access to lynx' source code doesn't
> > help. So IOCTLs are pretty much everywhere, much to my regret.
> That does not mean we will accept adding new ioctls for the Linux
> drivers, so I fail to see the point of this :)
I showed it just to point out that the vmelinux.org interface was
not very useful--I never said I'd like to see these IOCTLs merged.
I do *not* want to see those IOCTLs anywhere outside of our code,
and never did. Sorry for the confusion; hope it's clear now.
More information about the devel