| 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: <20080114165754.46e187f3@siona> Date: Mon, 14 Jan 2008 16:57:54 +0100 From: Haavard Skinnemoen <hskinnemoen@...el.com> To: Florian Fainelli <florian.fainelli@...ecomint.eu> Cc: Marc Pignat <marc.pignat@...s.ch>, linux-kernel@...r.kernel.org Subject: Re: [RFC, PATCH, take 2] watchdog on generic gpio On Mon, 14 Jan 2008 15:03:14 +0100 Florian Fainelli <florian.fainelli@...ecomint.eu> wrote: > Le lundi 14 janvier 2008, Marc Pignat a écrit : > > Hi Florian! > > I understand your wish, but... > > You told me that your plaform doesn't implement the generic gpio > > interface (yet?), so this driver can't work for you. > > You understood me wrong, I told you that not all platforms, actually > only AVR32 and ARM seem to make use of David Brownell's gpiolib, but > the MIPS board I am working with supports the "old" generic GPIO API > which required you to define your own wrappers for gpio_set/get_value > and such. For both implementations the config symbol is GENERIC_GPIO, > which can somehow be confusing. GENERIC_GPIO means that some implementation of the generic GPIO API is present. Gpiolib is a specific implementation of that API which architectures may choose to utilize -- it doesn't change anything that drivers should care about. Haavard -- 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