From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751682AbcGOAxV (ORCPT ); Thu, 14 Jul 2016 20:53:21 -0400 Received: from 216-12-86-13.cv.mvl.ntelos.net ([216.12.86.13]:59001 "EHLO brightrain.aerifal.cx" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751394AbcGOAxR (ORCPT ); Thu, 14 Jul 2016 20:53:17 -0400 Date: Thu, 14 Jul 2016 20:53:06 -0400 From: Rich Felker To: "Hans J. Koch" , Greg Kroah-Hartman Cc: linux-kernel@vger.kernel.org Subject: [PATCH RFC] uio: allow use on nommu systems Message-ID: <20160715005306.GA16591@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 --- 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 help Enable this to allow the userspace driver core code to be built. This code allows userspace programs easy access to -- 2.8.1