public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Rich Felker <dalias@libc.org>
Cc: "Hans J. Koch" <hjk@hansjkoch.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] uio: allow use on nommu systems
Date: Fri, 15 Jul 2016 10:42:37 +0900	[thread overview]
Message-ID: <20160715014237.GC5791@kroah.com> (raw)
In-Reply-To: <20160715005306.GA16591@brightrain.aerifal.cx>

On Thu, Jul 14, 2016 at 08:53:06PM -0400, Rich Felker wrote:
> mmap of uio devices does not seem to work without further
> nommu-specific support, but interrupt handling already works, and
> userspace drivers for nommu systems can simply use physical mmio
> addresses from userspace directly anyway without mmap.
> 
> Signed-off-by: Rich Felker <dalias@libc.org>
> ---
> 
> I don't particularly expect this to be accepted upstream as-is, but
> since we're actually trying to use the UIO subsystem on nommu (J2),
> I'd like to start a discussion of what an acceptable patch would
> entail.
> 
> The uio_pdrv_genirq driver was tested on J2 with this patch and
> interrupt handling works as expected.
> 
>  drivers/uio/Kconfig | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/uio/Kconfig b/drivers/uio/Kconfig
> index 52c98ce..387b2bb 100644
> --- a/drivers/uio/Kconfig
> +++ b/drivers/uio/Kconfig
> @@ -1,6 +1,5 @@
>  menuconfig UIO
>  	tristate "Userspace I/O drivers"
> -	depends on MMU

This doesn't seem to do much, don't you need to modify uio-specific
drivers?  Or given that the core uio code doesn't rely on mmu, is this
safe?

thanks,

greg k-h

  reply	other threads:[~2016-07-15  1:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15  0:53 [PATCH RFC] uio: allow use on nommu systems Rich Felker
2016-07-15  1:42 ` Greg Kroah-Hartman [this message]
2016-07-15  1:58   ` Rich Felker
2016-07-15 11:42     ` Greg Kroah-Hartman

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=20160715014237.GC5791@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dalias@libc.org \
    --cc=hjk@hansjkoch.de \
    --cc=linux-kernel@vger.kernel.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