kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: looking for decent, current online discussion of user-space drivers
Date: Tue, 17 Nov 2015 05:13:52 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.20.1511170508250.13936@localhost> (raw)


  a colleague asks me about the implications of porting a pile of code
from a non-linux embedded OS to linux, and simply rewriting most of it
as user-space drivers, as opposed to a total rewrite to kernel code.
i'm in no way an authority on user-space drivers, so i'm looking for
any decent, up-to-date discussions, not so much on the technical
aspects, but more the *implications* of doing this.

  i'm aware of mmap(), and i'm reading up on UIO, and i've found a few
online pieces that look informative:

http://www.embedded.com/design/operating-systems/4401769/Device-drivers-in-user-space
http://www.enea.com/Documents/Resources/Whitepapers/Enea-User-Space-Drivers-in-Linux_Whitepaper_2013.pdf

so is there something that elaborates on both the pros and cons of
doing this? in particular, are there any nice examples of this that
can be downloaded, built and played with? thanks muchly.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

             reply	other threads:[~2015-11-17 10:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17 10:13 Robert P. J. Day [this message]
2015-11-17 10:42 ` looking for decent, current online discussion of user-space drivers Anupam Kapoor
2015-11-17 10:46   ` Robert P. J. Day

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=alpine.LFD.2.20.1511170508250.13936@localhost \
    --to=rpjday@crashcourse.ca \
    --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 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).