Re: Persistent module storage [was Linux 2.4 Status / TODO page]

Gerhard Mack
2000-11-06T23:28:02Z

On Mon, 6 Nov 2000, James A. Sutherland wrote:

> Except this isn't possible with the hardware in question! If it were, there
> would be no problem. In cases where the hardware doesn't support the
> functionality userspace "needs", why put the kludge in the kernel?
>
> If userspace wants to know what settings it set last time, it should store
> those values somewhere.
>
> > jas88@cam.ac.uk said:
> > > The right thing in this context is not to screw with hardware
> > > settings unless and until it is given settings to set. Do not set
> > > values arbitrarily: set only the values you are explicitly given.
> > > Anything else is simply a bug in your driver.
> >
> > It is unwise to assume that the hardware is in a sane state when the driver
> > has been unloaded and reloaded. I agree that you should set the values that
> > were explicitly given. That's why we should remember them.
>
> No values are being explicitly given. Loading the driver should not cause
> any settings to be changed: changing the settings should do that!
>
> There is no need for the drivers to change any settings. If the settings need
> to be (re)set, let userspace do it.
>
>
> James.

Sure .. lets see you start a laptop in class or buisness meeting and have
everyone turn to look at you wondering why your laptop let off an ear
piercing shreak because the hardware defaults to all settings max.

And you will _STILL_ have that shriek for 1/2 - 1 second before the
userspace app loads.

And no we couldn't unplug either the mike or the speakers since they come
embedded in the laptop's case.

I don't see in any of your trolling an answer for this problem.

Gerhard

--
Gerhard Mack

gmack@innerfire.net

<>< As a computer I find your faith in technology amusing.