[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-id: <45CE533C.4010108@shaw.ca>
Date: Sat, 10 Feb 2007 17:20:28 -0600
From: Robert Hancock <hancockr@...w.ca>
To: nigel@...el.suspend2.net,
linux-kernel <linux-kernel@...r.kernel.org>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: NAK new drivers without proper power management?
Nigel Cunningham wrote:
> If your device requires power management, and you know it requires power
> management, why not just implement power management? Doing -ENOSYS
> instead is like saying -ESPAMMEBECAUSEIMLAZY.
>
> Let me put it another way: People keep talking about Linux being ready
> for the desktop. To me at least (but I dare say for lots of other people
> too), being ready for the desktop means that things just work, without
> having to recompile kernels or bug driver authors or wait twelve
> months.
>
> And it means that doing a bare minimum isn't enough. We keep claiming
> that Open Source is better than Proprietary software. If we accept
> half-pie jobs of implementing support for anything - driver power
> management support or hibernation support or whatever - as 'good
> enough', we're undercutting that argument. Linux's power management
> support should - as far as we're able - be at least as good as that
> other operating system's and preferably way, way better.
>
> -ENOSYS is just not acceptable.
Well, it's probably more acceptable than silently doing nothing and the
device failing or locking up the machine on resume, but I couldn't agree
more that it's not what we want to be encouraging. Perfect may be the
enemy of the good, but "works except no power management" is hardly what
I would call good these days, more like pretty sloppy..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@...pamshaw.ca
Home Page: http://www.roberthancock.com/
-
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