linux-kernel - Re: UIO device tree bindings.

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20130402115151.GA9052@amd.pavel.ucw.cz>
Date:	Tue, 2 Apr 2013 13:51:51 +0200
From:	Pavel Machek <pavel@...x.de>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	sr@...x.de, w.sang@...gutronix.de, magnus.damm@...il.com,
	hjk@...utronix.de, Greg KH <greg@...ah.com>,
	linux-kernel@...r.kernel.org, dzu@...x.de
Subject: Re: UIO device tree bindings.

On Mon 2013-04-01 19:42:12, Guenter Roeck wrote:
> On Mon, Apr 01, 2013 at 05:40:08PM +0200, Pavel Machek wrote:
> > On Mon 2013-04-01 16:23:36, Pavel Machek wrote:
> > > Hi!
> > > 
> > > I'd like to get uio device tree bindings to work -- with recent FPGA
> > > parts it will be important. Latest version I see is 
> > > 
> > > https://lists.ozlabs.org/pipermail/linuxppc-dev/2009-June/073087.html
> > > 
> > > ... Is there anything newer?
> > > 
> > > I red the discussion, and main problem seems to be the "tell kernel to
> > > drive this device tree device", right?
> > 
> Problem seems to be the notion that the proposed devicetree entry would not
> describe the hardware, but its use. Not really sure I understand the problem,
> as I would see the hardware description to be "A hardware device which is
> compatible to and managed by the generic-uio driver". I would argue that
> this _is_ a hardware description (if not, what is ?), but I am not the one
> to make the call.

Well... one could argue that having "generic-uio" in board's device
tree _is_ wrong, but having driver that binds to "generic-uio" is
not. Hmm?

Or maybe we can do some magic with module parameter. That should be
enough for expected use.

> > So... here's the port to recent kernels. Not for mainline.
> > 
> > Signed-off-by: Pavel Machek <pavel@...x.de>
> > 
> Turns out this is exactly what I need, and your post saves me the time
> I would have spent writing essentially the same code and submitting it,
> only to have it rejected.
> 
> Thanks a lot for digging this up!

You are welcome :-). Thanks for helping with testing ;-).
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/