All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Where to put the source of a DD of a custom hardware.
Date: Wed, 29 Oct 2014 10:40:37 +0800	[thread overview]
Message-ID: <20141029024037.GA7338@kroah.com> (raw)
In-Reply-To: <CAENGNhduTUdGJB2c13JtCRTSbf_ugzStNpMMBRoMZbkk=b9SdA@mail.gmail.com>

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

      reply	other threads:[~2014-10-29  2:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141029024037.GA7338@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.