From: CaT <cat@zip.com.au>
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.66
Date: Tue, 25 Mar 2003 18:22:30 +1100 [thread overview]
Message-ID: <20030325072230.GA496@zip.com.au> (raw)
In-Reply-To: <20030325065125.GA12590@kroah.com>
On Mon, Mar 24, 2003 at 10:51:25PM -0800, Greg KH wrote:
> On Tue, Mar 25, 2003 at 04:56:13PM +1100, CaT wrote:
> > > You will need the last one, I've attached it here. Let me know if it
> > > fixes this or not.
> >
> > I grabbed the entire patchset you posted for 2.5.66 and applied. Booted
> > without oops. Me happy. :)
>
> Nice, thanks for testing, I really appreciate it.
No worries. Glad to help. :)
One point of note though. Should this be happening?
i2c-dev.o: i2c /dev entries driver module version 2.7.0 (20021208)
i2c-proc.o version 2.7.0 (20021208)
i2c-piix4 version 2.7.0 (20021208)
piix4 smbus 00:07.3: Found Intel Corp. 82371AB/EB/MB PIIX4 device
i2c i2c-0: Error: no response!
i2c i2c-0: Error: no response!
i2c i2c-0: Error: no response!
i2c i2c-0: Error: no response!
i2c i2c-0: Error: no response!
i2c i2c-0: Error: no response!
i2c i2c-0: Error: no response!
registering i2c_dev_0
i2c i2c-0: Error: no response!
I only have the following compiled in:
# I2C support
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_PROC=y
CONFIG_I2C_PIIX4=y
CONFIG_SENSORS_ADM1021=y
I trimmed things down to this through testing (I compiled in many
options and then left only the ones that appeared in
/proc/sys/dev/sensors)
--
"Other countries of course, bear the same risk. But there's no doubt his
hatred is mainly directed at us. After all this is the guy who tried to
kill my dad."
- George W. Bush Jr, Leader of the United States Regime
September 26, 2002 (from a political fundraiser in Houston, Texas)
next prev parent reply other threads:[~2003-03-25 7:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 23:26 Linux 2.5.66 Linus Torvalds
2003-03-24 23:35 ` Larry McVoy
2003-03-25 0:14 ` Florin Iucha
2003-03-25 8:05 ` Rolf Eike Beer
2003-03-25 8:29 ` Marco Roeland
2003-03-25 0:16 ` Jeremy Brown
2003-03-25 0:22 ` Udo A. Steinberg
2003-03-25 0:30 ` Greg KH
2003-03-25 1:18 ` Udo A. Steinberg
2003-03-25 1:47 ` Greg KH
2003-03-25 4:18 ` CaT
2003-03-25 4:34 ` Greg KH
2003-03-25 5:56 ` CaT
2003-03-25 6:51 ` Greg KH
2003-03-25 7:22 ` CaT [this message]
2003-03-25 7:27 ` Greg KH
2003-03-25 0:53 ` John Cherry
2003-03-25 1:55 ` [REPRODUCABLE BUGS] " Toplica Tanaskovic
2003-03-25 3:19 ` James Simmons
2003-03-25 9:51 ` Toplica Tanaskovic
2003-03-26 20:24 ` James Simmons
2003-03-26 23:49 ` Torrey Hoffman
2003-03-27 0:20 ` James Simmons
2003-03-27 2:27 ` Joshua Kwan
2003-04-02 22:16 ` James Simmons
2003-04-03 1:02 ` Joshua Kwan
2003-04-03 3:59 ` James Simmons
2003-03-27 16:05 ` Toplica Tanaskovic
2003-03-26 2:53 ` Paweł Gołaszewski
2003-03-26 3:33 ` James Simmons
2003-03-26 11:00 ` [2.5 patch] fix sound/oss/mad16.c compile Adrian Bunk
2003-03-26 11:26 ` 2.5.66: compile problem with snd-ice1724 Adrian Bunk
2003-03-26 12:45 ` [2.5 patch] fix ipmi_devintf.c compilation Adrian Bunk
2003-03-26 14:36 ` Corey Minyard
-- strict thread matches above, loose matches on Subject: below --
2003-03-25 5:51 Linux 2.5.66 Andries.Brouwer
2003-03-26 10:45 ` Geert Uytterhoeven
2003-03-26 10:46 ` Geert Uytterhoeven
2003-03-25 7:40 Osamu Tomita
2003-03-26 11:52 Andries.Brouwer
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=20030325072230.GA496@zip.com.au \
--to=cat@zip.com.au \
--cc=greg@kroah.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox