[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070426145634.3ac2b7a3@hyperion.delvare>
Date: Thu, 26 Apr 2007 14:56:34 +0200
From: Jean Delvare <khali@...ux-fr.org>
To: "Jordan Crouse" <jordan.crouse@....com>
Cc: "Lennart Sorensen" <lsorense@...lub.uwaterloo.ca>,
"Haavard Skinnemoen" <hskinnemoen@...el.com>,
"David Brownell" <david-b@...bell.net>,
"Bryan Wu" <bryan.wu@...log.com>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Deepak Saxena" <dsaxena@...xity.net>,
linux-kernel@...r.kernel.org,
"Christer Weinigel" <wingel@...o-system.com>
Subject: Re: Bitbanging i2c bus driver using the GPIO API
On Mon, 23 Apr 2007 08:47:10 -0600, Jordan Crouse wrote:
> On 23/04/07 11:42 +0200, Jean Delvare wrote:
> > I seem to remember there has been a patch floating around to
> > auto-detect the right ports back in June 2006, but it seems to have
> > been lost somehow. Jordan, do you remember?
>
> I don't remember that, and Google isn't helping, either. Regardless,
> randomly hitting ISA ports seems scary to me. I know its a pain to use
> the module params all the time, but thats really probably the cleanest way
> to to it without carrying around a special patch for your system.
After digging some more, I finally managed to get my hands back on it:
http://lists.lm-sensors.org/pipermail/lm-sensors/2006-April/016009.html
http://lists.lm-sensors.org/pipermail/lm-sensors/2006-May/016053.html
This isn't "randomly hitting ISA ports", this is reading the base I/O
addresses from LPC configuration space. That's much better than letting
the user set the addresses using module parameters.
Lennart, can you please provide the output of the following commands on
your system?
isadump 0x2e 0x2f 5
isadump 0x2e 0x2f 6
isadump 0x4e 0x4f 5
isadump 0x4e 0x4f 6
(isadump is part of the lm_sensors package.)
--
Jean Delvare
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists