linux-kernel - Re: [PATCH v5] gpio: Add GPIO support for the WinSystems WS16C48

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20160128135058.GA16395@sophia>
Date:	Thu, 28 Jan 2016 08:50:58 -0500
From:	William Breathitt Gray <vilhelm.gray@...il.com>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Alexandre Courbot <gnurou@...il.com>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5] gpio: Add GPIO support for the WinSystems WS16C48

On Thu, Jan 28, 2016 at 09:47:43AM +0100, Linus Walleij wrote:
>Out of curiosity: what is your usecase for all these exotic
>GPIO cards?

My motivated mainly by philosophy. Despite their popularity in the
embedded systems industry, there isn't much support in the baseline
kernel for PC/104 and other cards. Typically, when a user purchases one
of these devices, they receive some general drivers which serve more as
proof that the device is working rather than as practical driver.

The user is lucky if they receive Linux drivers rather than just the
usual Windows drivers. Even if Linux drivers are provided, the drivers
are often written for ancient kernel versions (e.g. version 2.4), and
implement some custom character device structure rather than utilize the
Linux device model.

I'm writing these drivers to help bring support for these devices to the
baseline Linux kernel, in the hopes that it will be useful to someone,
and perhaps even motivate the companies to improve and share their own
Linux drivers.

William Breathitt Gray