From: Greg KH <greg@kroah.com>
To: CaT <cat@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-t1: i2c+sensors still whacky (hi Greg :)
Date: Wed, 16 Jul 2003 00:31:35 -0700 [thread overview]
Message-ID: <20030716073135.GA5338@kroah.com> (raw)
In-Reply-To: <20030716062922.GA1000@zip.com.au>
On Wed, Jul 16, 2003 at 04:29:22PM +1000, CaT wrote:
> On Tue, Jul 15, 2003 at 11:10:09PM -0700, Greg KH wrote:
> > On Wed, Jul 16, 2003 at 04:04:43PM +1000, CaT wrote:
> > > On Tue, Jul 15, 2003 at 09:11:27AM -0700, Greg KH wrote:
> > > Did I do the right thing?
> >
> > Looks good, but are you _really_ building all of those drivers into your
> > kernel? Make them modules, that way booting will not require a small
>
> No. Just i2c-dev, i2c-core, i2c-sensor, i2c-piix4 and adm1021. Sorry
> for not weeding out the useless stuff above. I was still waking up. :)
>
> > nap :)
>
> :)
>
> > Then load only the i2c bus driver that you have. See if that causes the
> > system to slow down, or cause any kernel log messages?
>
> i2c alone does not.
>
> > Only then try loading a i2c client driver, for your hardware.
>
> I can go through this again. Do you want me to insert any further
> debugging stuff?
>
> > Exactly what i2c hardware do you have anyway?
>
> PIIX4 and ADM1021.
>
> .config has the following:
>
> CONFIG_SENSORS_ADM1021=y
> CONFIG_I2C=y
> CONFIG_I2C_CHARDEV=y
> CONFIG_I2C_PIIX4=y
> CONFIG_I2C_SENSOR=y
Please change them to =m so that it's easier to try to debug this.
Then just load the i2c_piix4 module. If things still work just fine,
then try the i2c-adm1021 driver. See what the kernel log says then.
thanks,
greg k-h
next prev parent reply other threads:[~2003-07-16 7:17 UTC|newest]
Thread overview: 12+ 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 [this message]
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
2003-07-18 2:33 ` Greg KH
2003-07-21 7:37 ` CaT
2003-07-21 7:58 ` 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=20030716073135.GA5338@kroah.com \
--to=greg@kroah.com \
--cc=cat@zip.com.au \
--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;
as well as URLs for NNTP newsgroup(s).