Be sure you have remote access working (e.g. The display will show boot progress initially and then apply the last brightness setting.

If you play with this feature, please be aware that the setting is persistent across boots. Not what I was expecting to see based on Gordon's example where he echos a value of 80 to the backlight setting. Values below 128 unexpectedly turn the display off entirely. I was expecting to have brightness control, but writing values between 128 and 255 to /sys/class/backlight/rpi_backlight/brightness does not seem to have any effect on brightness. Just follow the old rule that the first 90% of the project takes the first 90% of the time, and the remaining 10% takes the other 90% of the time.įor more on these sorts of issues, go read Weinberg _The Psychology of Computer Programming_ and Brooks _The Mythical Man Month_.īacklight control is now working as of the firmware commit on Oct 21st I *think* the RPF has managed to escape the tendency of managers accepting what the programmer has said about schedule, then cutting that down to please the next management level up. If the programmer spends time talking about when he expects to be finished, that takes time away from getting it finished. Programmers tend to be optimistic about how long a project takes. And yeah I know that estimated times for programming can change a lot!

So if someone should know something about expected times, I would be glad to hear them. I don't think the coding will take that much time but depending on human resources, more important tasks and release cycles, it might take days, weeks or in worst case even months. But it would be nice to get some feedback about the estimated time until it is finished/published.

Raspberry pi sleep mode