linux-kernel - Re: [patch 2/5] Staging: vme: add VME userspace driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 10 Aug 2009 09:28:26 -0700
From:	Greg KH <gregkh@...e.de>
To:	"Emilio G. Cota" <cota@...ap.org>
Cc:	Martyn Welch <martyn.welch@...anuc.com>,
	linux-kernel@...r.kernel.org, devel@...uxdriverproject.org,
	Sebastien Dugue <sebastien.dugue@...l.net>
Subject: Re: [patch 2/5] Staging: vme: add VME userspace driver

On Sun, Aug 09, 2009 at 02:17:16PM +0200, Emilio G. Cota wrote:
> (oops, just correcting Sebastien's e-mail address)
> 
> Emilio G. Cota wrote:
> > I remember we had a look at the vmelinux interface, but it really
> > was so limited that we decided to get rid of it altogether. Do you
> > really think it's worth bringing it back to life? Since it's never
> > been merged into the kernel, why don't we just get it right this time
> > and forget about it?
> > 
> > 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?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/