linux-kernel - Re: [PATCH 1/2] Driver for user access to internal timer

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]

Date:	Thu, 8 Jan 2009 13:25:25 +0100
From:	"Hans J. Koch" <hjk@...utronix.de>
To:	Davide Rizzo <elpa.rizzo@...il.com>
Cc:	"Hans J. Koch" <hjk@...utronix.de>, linux-kernel@...r.kernel.org,
	gregkh@...e.de, ben-linux@...ff.org
Subject: Re: [PATCH 1/2] Driver for user access to internal timer

On Thu, Jan 08, 2009 at 12:37:04PM +0100, Davide Rizzo wrote:
> >
> > Davide,
> > please don't use drivers/uio/ for things that are no UIO drivers.
> >
> > Thanks,
> > Hans
> 
> I thought drivers/uoi is a better choice then driver/misc, because
> this driver allows user to access internal hardware to generate PWM
> signals.

Yes, but you do not use the UIO framework to achieve this.

> Otherwise, where do you suggest to put it ?

I didn't have a deeper look at your driver. I suggest you ask the people
who maintain the clock/timer frameworks you use. Since you seem to be
working on an ARM platform, you should Cc: the linux-arm-kernel mailing
list as well.

Thanks,
Hans

--
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/