[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Reassigning Bug#271814: who has to load acpi modules?

Hi d-developers, I need some help to find out who I have to reassign
this bug to (http://bugs.debian.org/271814), or else how to handle it.

Here's an excerpt from the discussion I had with the bug submitter:

--8<-- BEGIN
On Wed, 2004-09-15 at 16:49, Mattia Dongili wrote:
> On Wed, Sep 15, 2004 at 03:48:00PM +0200, Jan Mynarik wrote:
> > On Wed, 2004-09-15 at 15:40, Mattia Dongili wrote:
> > > what about loading ACPI modules earlier instead?
> > > Starting cpufreqd early at boot is a 'design' choice thus it can detect
> > > ac_on/ac_off and lower you cpuspeed as soon as possible.
> > 
> > Possible solution. Actually it's a problem of either cpufreqd or acpid
> > debian package. If you think it's better to start acpid earlier,
> > reassign the bug, please.
> actually I meant not to rely on a daemon to load important kernel
> modules, expecially if those modules ar not deamon-specific (eg: needed
> by other apps also).

Discover or hotplug doesn't load ACPI modules and I'm trying to keep my
/etc/modules minimal. Standard user would rather have ACPI modules
loaded automagically. So who should load them then? I don't think it up
to user, in that case, it would be huge usability regression.

I'd like to repeat that if you feel it's not cpufreqd's problem, please,
reassign it elsewhere (acpid, discover2, hotplug).
--8<-- END

It's certainly not a cpufreqd's duty, any suggestion?


Reply to: