| 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: <BANLkTim9_n85ahW781fGjf_iofhBjnD36w@mail.gmail.com> Date: Tue, 19 Apr 2011 09:45:10 -0600 From: Grant Likely <grant.likely@...retlab.ca> To: Arnd Bergmann <arnd@...db.de> Cc: John Williams <john.williams@...alogix.com>, Wolfram Sang <w.sang@...gutronix.de>, Michal Simek <monstr@...str.eu>, devicetree-discuss@...ts.ozlabs.org, linux-kernel@...r.kernel.org, hjk@...sjkoch.de Subject: Re: [PATCH v3] uio/pdrv_genirq: Add OF support On Tue, Apr 19, 2011 at 9:07 AM, Arnd Bergmann <arnd@...db.de> wrote: > On Tuesday 19 April 2011, Grant Likely wrote: >> > or whatever, as this would bind all instances matching vendor,device. >> > >> > So, the question I have is, how to handle bind per-instance? >> >> By manipulating a property on the device instance of course! :-) >> >> Something like: echo "generic-uio" >> >> /sys/devices/path/to/device/a-property-that-changes-the-driver-it-will-bind-to. >> > > But what code would create that in sysfs, and based on what properties > of the device? Should we do that for every platform device, or perhaps > for every one that has any resources? Yes, I think it can be a generic facility for all platform_devices. We already have some code to support user-space manipulated driver binding/unbinding. This is very much in the same vein. g. -- 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