All of lore.kernel.org
 help / color / mirror / Atom feed
From: mds4@verizon.net (Mark Studebaker)
To: lm-sensors@vger.kernel.org
Subject: checksum in (i2c) eeprom driver
Date: Thu, 19 May 2005 06:25:26 +0000	[thread overview]
Message-ID: <41B85D43.8070409@verizon.net> (raw)
In-Reply-To: <lNsWdTVB.1102596784.6279250.khali@localhost>

I think the checksum code is useful because checksum=1 prevents the module from claiming ddc monitor eeproms
and other devices in its address space 50-57.
Since detection for eeproms is otherwise poor, it's the only way we have for robust detection.

Jean Delvare wrote:
> Hi all,
> 
> Any objection to me removing the checksumming code from the (i2c) eeprom
> driver? Deepak had suggested we should do so a long time ago [1], and I
> fully agree with his position. The checksum is application-specific and
> verifying it doesn't belong to the kernel-space. The checksumming code
> we (optionally) use at the moment only covers memory module EEPROMs as
> far as I know, while EEPROMs exposed on I2C/SMBus may be of a variety of
> other natures.
> 
> [1] http://archives.andrew.net.au/lm-sensors/msg21194.html
> 
> Thanks,
> --
> Jean Delvare
> 
> 

  parent reply	other threads:[~2005-05-19  6:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-09 12:53 checksum in (i2c) eeprom driver Jean Delvare
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Mark Studebaker
2004-12-10  8:42   ` Jean Delvare
2005-05-19  6:25     ` Jean Delvare
2004-12-15  0:57     ` Mark M. Hoffman
2005-05-19  6:25       ` Mark M. Hoffman
2004-12-15  9:17       ` Jean Delvare
2005-05-19  6:25         ` Jean Delvare
2005-05-19  6:25 ` Mark Studebaker [this message]
2004-12-09 14:45   ` Jean Delvare
2005-05-19  6:25     ` Jean Delvare
2004-12-09 23:17     ` Greg KH
2005-05-19  6:25       ` Greg KH

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=41B85D43.8070409@verizon.net \
    --to=mds4@verizon.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.