All of lore.kernel.org
 help / color / mirror / Atom feed
From: mds@paradyne.com (Mark Studebaker)
To: lm-sensors@vger.kernel.org
Subject: i2c for Alpha
Date: Thu, 19 May 2005 06:24:21 +0000	[thread overview]
Message-ID: <3F9484A0.F04F940@paradyne.com> (raw)
In-Reply-To: <200310121707.56799.jeff@jdfiles.org>

'make -k' lets you keep building after an error which is easier than
editing Module.mk.


Jean Delvare wrote:
> 
> > > I suspect that you tried to update lm_sensors to 2.8.0 but did not
> > > update i2c to 2.8.0 preliminarily. Do that and it should work OK.
> > > You
> >
> > I built i2c outside the kernel using a package for my distribution.
> 
> Still it needs to be a version equal to or greater than the version of
> lm_sensors you are trying to install. Also, make sure that lm_sensors
> picks the right header files. If you have old i2c header files lying
> around in /usr/local/include or /use/include, you might want to wipe
> them out to make sure the newer ones are used.
> 
> > > might want to take a look at our installation guide at
> > > http://www.ensicaen.ismra.fr/~delvare/devel/i2c/ since installing
> > > i2c 2.8.0 is somewhat tricky.
> >
> > Is it still the case with 2.8.1, that you have to have the kernel
> > patch applied to build?
> 
> Yes, you have.
> I'm currently working on an i2c patch for submission into Linux 2.4.23
> so that lm_sensors will be easier to install, but for now you are
> advised to stick to the installation guide says.
> 
> That said, Philip Edelbrock's remark is absolutely right. Some, if not
> most, drivers of our package are useless on Alpha, so if a particular
> driver doesn't compile for some reason, and you know you won't need it,
> just remove it from Module.mk so that it isn't compiled at all.
> 
> --
> Jean Delvare
> http://www.ensicaen.ismra.fr/~delvare/

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

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:24 i2c for Alpha Jeff Sacksteder
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Philip Edelbrock
2005-05-19  6:24 ` Jeff Sacksteder
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Jeff Sacksteder
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Morris, John
2005-05-19  6:24 ` jeff
2005-05-19  6:24 ` Mark Studebaker [this message]
2005-05-19  6:24 ` Philip Edelbrock
2005-05-19  6:24 ` Philip Edelbrock
2005-05-19  6:24 ` Jeff Sacksteder
2005-05-19  6:24 ` Mark Studebaker
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` jeff
2005-05-19  6:24 ` jeff
2005-05-19  6:24 ` Jeff Sacksteder
2005-05-19  6:24 ` Jeff Sacksteder

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=3F9484A0.F04F940@paradyne.com \
    --to=mds@paradyne.com \
    --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.