From: "Mark M. Hoffman" <mhoffman@lightlink.com>
To: Etienne Lorrain <etienne_lorrain@yahoo.fr>
Cc: linux-kernel@vger.kernel.org,
lm-sensors <lm-sensors@lm-sensors.org>,
Ian Campbell <icampbell@arcom.com>
Subject: Re: I2C_PCA_ISA causes boot delays (was re: sis96x compiled in by error: delay of one minute at boot)
Date: Wed, 29 Mar 2006 08:38:35 -0500 [thread overview]
Message-ID: <20060329133835.GB8309@jupiter.solarsys.private> (raw)
In-Reply-To: <20060329092628.16392.qmail@web26908.mail.ukl.yahoo.com>
Hello Etienne:
* Etienne Lorrain <etienne_lorrain@yahoo.fr> [2006-03-29 11:26:28 +0200]:
> --- "Mark M. Hoffman" <mhoffman@lightlink.com> wrote:
> > > 885c885
> > > < # CONFIG_I2C_PCA_ISA is not set
> > > ---
> > > > CONFIG_I2C_PCA_ISA=y
> >
> > This alone is the cause of the delay. (I have confirmed it by running some
> > similar .configs here.) You almost certainly don't own this specialized
> > piece of hardware. Worse still, that particular driver has no code to detect
> > whether or not the hardware is present. I cc'ed the listed driver author
> > (Ian) just in case this might be corrected... but I guess there is no way
> > to fix it.
> >
> > So the delay is (1) an I2C bus driver that is not actually present, trying to
> > probe for (2) seven different sensors chip drivers that certainly aren't present
> > on the nonexistent bus. Timeouts ensue.
> >
> > So unless Ian knows a better way to detect that bus driver... the best I can
> > advise is to *not* build in those drivers for hardware that you do not have.
>
> OK, I know the I2C protocol, and I can imagine a hardware board which does
> not have a way to detect its own presence - or the presence of its own ISA bus.
> What I dislike the most is that, after the driver has taken more than 20
> seconds to probe something it did not find, it did not display anything to
> say "either there is a hardware problem, or you should disable me".
I repeat just once more: the supported method for identifying hwmon/sensors
chips is a Perl script called sensors-detect that is distributed with the
lm-sensors package.
> Are you sure that there isn't any distribution around trying to insert
> _all_ the modules to do hardware detection?
No, because that is not supported. All of the major distributions package
lm-sensors, and AFAIK they all build hwmon/sensors as modules. They don't
insert any of them by default. If a distro was silly enough to blindly
insert them all... then it would take forever to boot and nobody would use
it.
> Note that most I2C driver detect abscence of the hardware in a lot less than
> a second: most of the I2C system is fine.
Feel free to write a patch for drivers/busses/i2c/i2c-pca-isa.c; I don't
have that hardware myself. Otherwise, my final advice is:
Patient: It hurts when I do this.
Doctor: Don't do that.
Regards,
--
Mark M. Hoffman
mhoffman@lightlink.com
next prev parent reply other threads:[~2006-03-29 13:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 10:27 sis96x compiled in by error: delay of one minute at boot Etienne Lorrain
2006-03-13 11:46 ` Jean Delvare
2006-03-13 22:38 ` Etienne Lorrain
2006-03-14 9:43 ` Jean Delvare
2006-03-15 3:46 ` Mark M. Hoffman
2006-03-15 9:01 ` Jean Delvare
2006-03-16 3:59 ` Mark M. Hoffman
2006-03-16 8:46 ` Jean Delvare
2006-03-16 10:53 ` Etienne Lorrain
2006-03-17 4:20 ` [lm-sensors] " Mark M. Hoffman
2006-03-20 23:00 ` Etienne Lorrain
2006-03-29 3:45 ` I2C_PCA_ISA causes boot delays (was re: sis96x compiled in by error: delay of one minute at boot) Mark M. Hoffman
2006-03-29 9:26 ` Etienne Lorrain
2006-03-29 13:38 ` Mark M. Hoffman [this message]
2006-03-29 14:00 ` Ian Campbell
2006-03-17 3:56 ` [lm-sensors] sis96x compiled in by error: delay of one minute at boot Mark M. Hoffman
2006-03-17 3:58 ` [PATCH 2.6.16-rc6] i2c: require type parameter for i2c-parport and i2c-parport-light Mark M. Hoffman
2006-03-22 12:32 ` Jean Delvare
2006-03-15 23:03 ` [ot] VIA southbridge strangeness (was: sis96x compiled in by error: delay of one minute at boot) Jan Engelhardt
2006-03-16 8:22 ` Jean Delvare
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=20060329133835.GB8309@jupiter.solarsys.private \
--to=mhoffman@lightlink.com \
--cc=etienne_lorrain@yahoo.fr \
--cc=icampbell@arcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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
all inboxes | Powered by JetHome®