From: reuben-lmsensors@reub.net (Reuben Farrelly)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Re: it87 and lm85 tickets
Date: Sat, 26 Nov 2005 14:29:03 +0000 [thread overview]
Message-ID: <43886314.8090806@reub.net> (raw)
In-Reply-To: <42374305.6030000@mds.gotdns.com>
Hi all,
[this is a resend, previously resent to the old mailing list address a few days
ago which now bounces]
Not sure where we got with this bug (started off at
http://www2.lm-sensors.nu/~lm78/readticket.cgi?ticket\x1933) but thought I'd
follow up, as I may have been the one holding things up in the past.
Note that this is with my second (slightly older) Intel board, completely
separate issue to the ADT7476ARQZ chip detection which I posted about earlier today.
On 29/03/2005 4:15 a.m., Philip Pokorny wrote:
> Reuben Farrelly wrote:
>
>> Hi Philip,
>>
>> Philip Pokorny wrote:
>>
>>> Jean Delvare wrote:
>>>
>>>>> lm85 new stepping 0x69: ticket 1933 (khali)
>>>>>
>>>>
>>>>
>>>>
>>>> I AM NOT THE LM85 GUY!
>>>>
>>>> The driver was written and is maintained by Philip Pokorny and Justin
>>>> Thiessen at Penguin Computing.
>>>>
>>>> #1933: [waiting for user data]
>>>>
>>>>
>>>
>>> So, I guess I *am* the LM85 guy.
>>>
>>> Yes, please send or reply with 'i2c-dump 0 0x2e' when lm85 is *not*
>>> loaded.
>>
>>
>> Here you go..
>>
>> [root@typhoon ~]# i2cdump 0 0x2e
>> No size specified (using byte-data access)
>> WARNING! This program can confuse your I2C bus, cause data loss and
>> worse!
>> I will probe file /dev/i2c-0, address 0x2e, mode byte
>> Continue? [Y/n]
>> 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
>> 30: 4d 4d 4d 00 00 00 00 00 00 00 00 00 00 00 01 69 MMM...........?i
>
>
> So this says that it's a National Semiconductor part (0x3e is 0x01) and
> that's it's *not* an LM85 (0x3f is 0x69) but according to the lm96000
> datasheet it is a superset of the lm85 functionality. Unfortunately,
> the only value listed for 0x3f in the lm96000 datasheet is 0x68.
>
> So, most likely this is a later version of the lm96000.
>
>>
>> Probing for `National Semiconductor LM85 or LM96000'... Success!
>> (confidence 7, driver `lm85')
>
>
> That's helpful. Thanks Khali...
>
>>
>> The chip is pretty hard to locate on the board but if it's really
>> necessary I can try again :(
>
>
> You might check again. But instead of looking for a chip with "LM85",
> look for a 24-pin surface mount package with "LM96???" on it. It will
> be smaller than the keys on your keyboard, but larger than the tip of a
> pen or pencil.
I've put a picture of the chip up online at http://www.reub.net/files/kernel/
and can confirm that it is an LM96000 chip.
This is still an issue in current kernels (2.6.15-rc2-mm1 at least), as I'm
still seeing the warning message when booting up:
i2c_adapter i2c-0: Unrecognized version/stepping 0x69 Defaulting to LM85.
Is there anything else I can do to get the ball rolling on this again?
Most if not all of the functionality is there with the LM85 so it's not a
showstopper.
Thanks,
Reuben
prev parent reply other threads:[~2005-11-26 14:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:25 it87 and lm85 tickets Mark Studebaker
2005-05-19 6:25 ` Philip Pokorny
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Reuben Farrelly
2005-05-19 6:25 ` Philip Pokorny
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Philip Pokorny
2005-05-19 6:25 ` Mark Studebaker
2005-11-26 14:29 ` Reuben Farrelly [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43886314.8090806@reub.net \
--to=reuben-lmsensors@reub.net \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.