Re: [lm-sensors] [RFC] (almost) booting allyesconfig -- please don't poke super-io without request_region

2008-07-13 Thread David Hubbard
Hi Hans, Milton, Jean, On Sun, Jul 13, 2008 at 12:31 AM, Hans de Goede <[EMAIL PROTECTED]> wrote: > Jean Delvare wrote: >> On Fri, 11 Jul 2008 09:27:26 +0200, Hans de Goede wrote: >>> Jean Delvare wrote: Hi Hans, hi Milton, >>> >>> > One could make a superio driver, and create sub-d

Re: [lm-sensors] [RFC] (almost) booting allyesconfig -- please don't poke super-io without request_region

2008-07-13 Thread David Hubbard
Hi Hans, >> I propose writing a subsystem driver. (Is that properly called "The >> SuperIO Bus Driver"?) If no one thinks it's a really bad idea I will >> put together some code and submit it for review, and maintain it. >> >> Some hwmon chips have odd / unique probe sequences. IMHO this is where

Re: [lm-sensors] [RFC] (almost) booting allyesconfig -- please don't poke super-io without request_region

2008-07-14 Thread David Hubbard
Hi Hans, On Mon, Jul 14, 2008 at 11:30 AM, Hans de Goede <[EMAIL PROTECTED]> wrote: > Milton Miller wrote: >> I haven't done the research, but it might be keep superio as >> a platform driver, and keep the clients as platform drivers. Only >> have the superio driver probe and discover the subcomp

Re: [RFC] (almost) booting allyesconfig -- please don't poke super-io without request_region

2008-07-15 Thread David Hubbard
Hi Jean, On Tue, Jul 15, 2008 at 2:36 AM, Jean Delvare <[EMAIL PROTECTED]> wrote: >> Is there any way to use lspci and start at the LPC bridge, then find >> the SuperIO chip's IO address? What about ACPI tables? Perhaps probing >> logic could look for an LPC bridge before probing certain IO addres