* Where to put the source of a DD of a custom hardware.
@ 2014-10-28 17:58 Raphael Philipe
2014-10-29 2:40 ` Greg KH
0 siblings, 1 reply; 2+ messages in thread
From: Raphael Philipe @ 2014-10-28 17:58 UTC (permalink / raw)
To: kernelnewbies
Hi,
I'm developing a device driver to drive a specific custom hardware,
that is implemented in FPGA. Since it is an application specific
device driver, where (in witch folder) should I put Its source in my
local kernel source tree? Is there any guideline or best practice
about it?
This device driver is basically a character device, that copies stuff
from hardware to kernel space and then from user space.
Regards,
Raphael
^ permalink raw reply [flat|nested] 2+ messages in thread
* Where to put the source of a DD of a custom hardware.
2014-10-28 17:58 Where to put the source of a DD of a custom hardware Raphael Philipe
@ 2014-10-29 2:40 ` Greg KH
0 siblings, 0 replies; 2+ messages in thread
From: Greg KH @ 2014-10-29 2:40 UTC (permalink / raw)
To: kernelnewbies
On Tue, Oct 28, 2014 at 03:58:40PM -0200, Raphael Philipe wrote:
> Hi,
>
> I'm developing a device driver to drive a specific custom hardware,
> that is implemented in FPGA. Since it is an application specific
> device driver, where (in witch folder) should I put Its source in my
> local kernel source tree? Is there any guideline or best practice
> about it?
>
> This device driver is basically a character device, that copies stuff
> from hardware to kernel space and then from user space.
Why not just use the UIO interface, which does not need a kernel driver
at all? Why are you needing a char driver?
thanks,
greg k-h
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-10-29 2:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-10-28 17:58 Where to put the source of a DD of a custom hardware Raphael Philipe
2014-10-29 2:40 ` Greg KH
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).