public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ijc@hellion.org.uk>
To: "Mark M. Hoffman" <mhoffman@lightlink.com>
Cc: Etienne Lorrain <etienne_lorrain@yahoo.fr>,
	linux-kernel@vger.kernel.org,
	lm-sensors <lm-sensors@lm-sensors.org>
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 15:00:07 +0100	[thread overview]
Message-ID: <1143640808.22244.26.camel@localhost.localdomain> (raw)
In-Reply-To: <20060329034510.GA8309@jupiter.solarsys.private>

On Tue, 2006-03-28 at 22:45 -0500, Mark M. Hoffman wrote:
> 
> 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. 

I don't work at Arcom anymore so I don't have access to the hardware,
but I don't know of a better way off the top of my head how to detect
the presence of the PCA chip.

You are unlikely to have the particular PC/104 card the driver was
written for. If I recall correctly PCA chip itself doesn't do ISA (it
has simple processor bus chip select type arrangement I think) but the
PC/104 card in question has a small CPLD which does the address decoding
for ISA. I guess you are unlikely to find another ISA card which has the
PCA chip on it.

It's possible that you might have an embedded board with the PCA chip
directly on it -- but if you don't then I don't know why you would
enable the driver.

Ian.
-- 
Ian Campbell

To save a single life is better than to build a seven story pagoda.


  parent reply	other threads:[~2006-03-29 13:58 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
2006-03-29 14:00                       ` Ian Campbell [this message]
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=1143640808.22244.26.camel@localhost.localdomain \
    --to=ijc@hellion.org.uk \
    --cc=etienne_lorrain@yahoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=mhoffman@lightlink.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