On Tue, 22 Jan 2008, Matthew Garrett wrote:Actually, no, it is not implicit. The spec clearly states that the brightness values will be cycled through the ones given by that list. It is implicit that brightness up actions will cycle through the list in order, and brightness down will cycle through the list in reverse order. If a vendor where to decide to place the most used brightness values in the beginning of the list, and the rest of it later, he would be allowed to do so. Nobody was weird enough to do it yet though, AFAIK. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh --
| Greg Kroah-Hartman | [PATCH 006/196] Chinese: add translation of oops-tracing.txt |
| Linus Torvalds | Linux 2.6.21-rc1 |
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
| Alexey Dobriyan | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Evgeniy Polyakov | Re: [BUG] New Kernel Bugs |
git: | |
