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

[Hans de Goede]

Jean Delvare wrote:
> On Fri, 11 Jul 2008 09:27:26 +0200, Hans de Goede wrote:
> > Jean Delvare wrote:
> > > Hi Hans, hi Milton,
> > <snip>
> >
> > > > One could make a superio driver, and create sub-devices for the IR, 
> > > > I2C, floppy, parallel, etc
> > > > nodes.
> > > There have been proposals to do this, and this would indeed be a very
> > > good idea, but unfortunately nobody took the time to implement this
> > > properly, push it upstream and volunteer to maintain it. The problem is
> > > that you don't need just a "driver", but a new subsystem, that needs to
> > > be designed and maintained.
> > Well, I believe there have been some lightweight superio locking coordinator 
> > patches been floating around on the lm_sensors list, and I have reviewed them 
> > and then a new version was done with my issues fixed.
> >
> > I kinda liked the proposed solution there, it was quite simple, moved all the 
> > generic superio stuff into generic superio code, and added locking for super io 
> > access from multiple drivers, what ever happened to those patches?
>
> As far as I know, nothing, and this is the problem. Somebody needs to
> step up and call him/herself the maintainer of the new code, and push
> it upstream and convert all the drivers (hwmon, watchdog, parallel
> port...) to make use of it. And I am not the one to do this, I am busy
> enough as is with i2c and hwmon.

Ok, I've mailed Jim Cromie, the author of the superio access patches 
from end 2007 and told him we're still interested in this and asked him 
if he is willing to drive this forward.

Regards,

Hans

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/