From: CaT <cat@zip.com.au>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, frodol@dds.nl, phil@netroedge.com
Subject: Re: 2.5.66: The I2C code ate my grandma...
Date: Sat, 5 Apr 2003 10:59:50 +1000 [thread overview]
Message-ID: <20030405005950.GA464@zip.com.au> (raw)
In-Reply-To: <20030404171424.GA1380@kroah.com>
On Fri, Apr 04, 2003 at 09:14:24AM -0800, Greg KH wrote:
> So if you disable the I2C config items, everything works just fine?
Yup.
> I did send out a bugfix for the i2c code for a problem in 2.5.66, it's
> now included in the latest -bk tree. Could you grab that patch and see
> if it fixes your problem?
Ok. Running -bk10. Where, umm, is the userspace interface to it? I can't
find anything in /proc or /sys so I can't see if it's actually working.
Incase they're useful here are snippets from .config and dmesg:
# I2C support
CONFIG_I2C=y
# CONFIG_I2C_ALGOBIT is not set
# CONFIG_I2C_ALGOPCF is not set
CONFIG_I2C_CHARDEV=y
# I2C Hardware Sensors Mainboard support
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
CONFIG_I2C_PIIX4=y
# I2C Hardware Sensors Chip support
CONFIG_SENSORS_ADM1021=y
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_W83781D is not set
CONFIG_I2C_SENSOR=y
i2c-dev.o: i2c /dev entries driver module 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 0-004d
i2c i2c-0: Error: no response!
One question. Will I need ISA support in the kernel for this?
--
Martin's distress was in contrast to the bitter satisfaction of some
of his fellow marines as they surveyed the scene. "The Iraqis are sick
people and we are the chemotherapy," said Corporal Ryan Dupre. "I am
starting to hate this country. Wait till I get hold of a friggin' Iraqi.
No, I won't get hold of one. I'll just kill him."
- http://www.informationclearinghouse.info/article2479.htm
next prev parent reply other threads:[~2003-04-05 0:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 2:11 2.5.66: The I2C code ate my grandma CaT
2003-04-04 17:14 ` Greg KH
2003-04-05 0:59 ` CaT [this message]
2003-04-05 1:14 ` Greg KH
2003-04-05 1:16 ` CaT
2003-04-05 1:24 ` Greg KH
2003-04-05 1:45 ` 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=20030405005950.GA464@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 \
/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