linux-kernel - Re: [i2c] [PATCH v2] Add support for Dallas DS28CM00 Unique ID chip

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 for Android: free password hash cracker in your pocket

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

Message-ID: <48FE3017.4080009@mimc.co.uk>
Date:	Tue, 21 Oct 2008 20:40:07 +0100
From:	Mark Jackson <mpfj@...c.co.uk>
To:	Jean Delvare <khali@...ux-fr.org>
CC:	i2c@...sensors.org, lkml <linux-kernel@...r.kernel.org>
Subject: Re: [i2c] [PATCH v2] Add support for Dallas DS28CM00 Unique ID chip

Mark Jackson wrote:
> Jean Delvare wrote:
>> Hi Mark,
>>
>> On Tue, 21 Oct 2008 19:42:42 +0100, Mark Jackson wrote:
>>> Jean Delvare wrote:
>>>> Nack. No new drivers under drivers/i2c/chips please, it's going away
>>>> soon.
>>> Okay ... where should any new drivers be located ?
>>
>> Depends of what the device does.
>> * Hardware monitoring chip drivers go to drivers/hwmon
>> * RTC chip drivers go to drivers/rtc
>> * I/O expander drivers go to drivers/gpio
>> If you can't find a suitable directory under drivers, either create a
>> new one if that makes sense, or put your driver under drivers/misc.
> 
> Ah, now I understand !!  I think drivers/misc is probably a good a place 
> as any,

In fact, I now realise that the device is *really* just a read-only eeprom.

So I'm guessing I don't need a custom driver, I can just use the existing
"at24" driver.

Ho hum ...
--
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/