| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20131022234835.GB12031@kroah.com> Date: Wed, 23 Oct 2013 00:48:35 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: Bin Gao <bin.gao@...ux.intel.com> Cc: Guenter Roeck <linux@...ck-us.net>, Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org Subject: Re: [PATCH 0/4] drivers/misc: add rawio framework and drivers On Tue, Oct 22, 2013 at 11:50:04AM -0700, Bin Gao wrote: > On Tue, Oct 22, 2013 at 10:14:00AM -0700, Guenter Roeck wrote: > > > > > > You can already do this today for PCI with the UIO framework, right? > > > Why duplicate that functionality here with another userapce API that we > > > will then have to maintain for the next 40+ years? > > > > > Same for i2c, where the same functionality is supported through i2c-tools and > > the i2c-dev driver. Adding i2c-tools to initramfs and/or to the root file system > > should not be that much of an issue, much less than having to maintain two APIs > > for the same purpose. > > > > Guenter > > For PCI and memory mapped I/O devices, we have the runtime pm issue that has to > be addressed from kernel space. Then create a UIO pci driver and you should be fine, right? That's what others do today and it works quite well for them. greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists