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: <E04775E6-5FCA-436E-BA3A-6D53691070BB@niasdigital.com>
Date:	Fri, 5 Nov 2010 18:38:24 +1100
From:	Ben Nizette <bn@...sdigital.com>
To:	Maciej Szmigiero <mhej@...pl>
Cc:	Jonathan Cameron <jic23@....ac.uk>, johnpol@....mipt.ru,
	linux-kernel@...r.kernel.org,
	David Brownell <dbrownell@...rs.sourceforge.net>
Subject: Re: [W1] a driver for DS2405 chip


On 05/11/2010, at 9:15 AM, Maciej Szmigiero wrote:

> W dniu 04.11.2010 22:16, Ben Nizette pisze:
>> 
>> On 05/11/2010, at 7:01 AM, Maciej Szmigiero wrote:
>> 
>> Well that and standardisation!  However it does seem that while conceptually your device should present a gpio interface it's on the fringe
>> of what gpiolib was designed to do.  I'd understand if you don't feel like making gpiolib better support hotpluggable devices however it
>> sounds like it'd be worth doing, not just for 1-W but also, eg, USB GPIO expanders.
> 
> So in your opinion is it worth "bending" the GPIO subsystem to accommodate devices like this one?
> This doesn't seem very hard if that parent thing works, just one new function (gpiochip_remove_blocking() or similar).
> 

s/bending/extending ;-)

I don't reckon it'll be long until someone starts trying to connect up other 1-W/USB/otherwise-hotpluggable expanders through gpiolib and if there are roadblocks they should be addressed.

David has the last word of course but I quite like the idea.

> Anyway, thanks for helping make the code better!

:-)

> 
>> 	--Ben.
> 
> Maciej Szmigiero

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ