All of lore.kernel.org
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: Greg KH <greg@kroah.com>
Cc: sensors@stimpy.netroedge.com, frodol@dds.nl,
	linux-kernel@vger.kernel.org, phil@netroedge.com
Subject: Re: 2.6.0-t1: i2c+sensors still whacky
Date: Mon, 21 Jul 2003 17:58:15 +1000	[thread overview]
Message-ID: <20030721075815.GC640@zip.com.au> (raw)
In-Reply-To: <20030721073753.GA640@zip.com.au>

On Mon, Jul 21, 2003 at 05:37:54PM +1000, CaT wrote:
> On Thu, Jul 17, 2003 at 07:33:51PM -0700, Greg KH wrote:
> > On Fri, Jul 18, 2003 at 01:33:48AM +1000, CaT wrote:
> > > > sensors package for 2.4 uses?  And 2.4 works just fine, right?
> > > 
> > > I don't use 2.4. Haven't for ages.
> > 
> > I would _really_ encourage you to try this, and run the sensors_detect
> 
> Good thing you did. :)

Gah. Too tired. I used the following:

linux kernel 2.4.22-pre7
lm sensors 2.8.0
i2c 2.8.0

Did not use inbuilt i2c.

-- 
"How can I not love the Americans? They helped me with a flat tire the
other day," he said.
	- http://tinyurl.com/h6fo

WARNING: multiple messages have this Message-ID (diff)
From: cat@zip.com.au (CaT)
To: Greg KH <greg@kroah.com>
Cc: sensors@stimpy.netroedge.com, frodol@dds.nl,
	linux-kernel@vger.kernel.org, phil@netroedge.com
Subject: 2.6.0-t1: i2c+sensors still whacky
Date: Thu, 19 May 2005 06:24:06 +0000	[thread overview]
Message-ID: <20030721075815.GC640@zip.com.au> (raw)
In-Reply-To: <20030721073753.GA640@zip.com.au>

On Mon, Jul 21, 2003 at 05:37:54PM +1000, CaT wrote:
> On Thu, Jul 17, 2003 at 07:33:51PM -0700, Greg KH wrote:
> > On Fri, Jul 18, 2003 at 01:33:48AM +1000, CaT wrote:
> > > > sensors package for 2.4 uses?  And 2.4 works just fine, right?
> > > 
> > > I don't use 2.4. Haven't for ages.
> > 
> > I would _really_ encourage you to try this, and run the sensors_detect
> 
> Good thing you did. :)

Gah. Too tired. I used the following:

linux kernel 2.4.22-pre7
lm sensors 2.8.0
i2c 2.8.0

Did not use inbuilt i2c.

-- 
"How can I not love the Americans? They helped me with a flat tire the
other day," he said.
	- http://tinyurl.com/h6fo

  reply	other threads:[~2003-07-21  7:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15  9:07 2.6.0-t1: i2c+sensors still whacky (hi Greg :) CaT
2003-07-15 16:11 ` Greg KH
2003-07-16  6:04   ` CaT
2003-07-16  6:10     ` Greg KH
2003-07-16  6:29       ` CaT
2003-07-16  7:31         ` Greg KH
2003-07-16 22:47           ` CaT
2003-07-16 22:54             ` Greg KH
2003-07-17 15:33               ` 2.6.0-t1: i2c+sensors still whacky CaT
2005-05-19  6:24                 ` CaT
2003-07-18  2:33                 ` Greg KH
2005-05-19  6:24                   ` Greg KH
2003-07-21  7:37                   ` CaT
2005-05-19  6:24                     ` CaT
2003-07-21  7:58                     ` CaT [this message]
2005-05-19  6:24                       ` CaT

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=20030721075815.GC640@zip.com.au \
    --to=cat@zip.com.au \
    --cc=frodol@dds.nl \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phil@netroedge.com \
    --cc=sensors@stimpy.netroedge.com \
    /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.