From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Subject: Re: identify i2c Date: Sun, 20 May 2012 17:17:14 -0400 Message-ID: <4FB95F5A.30003@lockie.ca> References: <4FB952EB.1050505@lockie.ca> <20120520230047.45aaa1c0@endymion.delvare> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20120520230047.45aaa1c0-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org> Sender: linux-i2c-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-i2c@vger.kernel.org On 05/20/12 17:00, Jean Delvare wrote: > On Sun, 20 May 2012 16:24:11 -0400, James wrote: >>> # decode-dimms >>> # decode-dimms version 5929 (2011-02-16 14:58:38 +0100) >>> >>> Memory Serial Presence Detect Decoder >>> By Philip Edelbrock, Christian Zuckschwerdt, Burkart Lingner, >>> Jean Delvare, Trent Piepho and others >>> No EEPROM found, are you sure the eeprom module is loaded? >> >> How do I find out what to configure in a 3.4 kernel? > > CONFIG_I2C=y > CONFIG_EEPROM_LEGACY=m > > Plus CONFIG_I2C_=m. "lspci | grep SMBus" etc. might > tell you which it is. > How do I find CONFIG_EEPROM_LEGACY in menuconfig? I manually changed it in .config :-)