Hello,
I did write a script to easily set the screen brightness. I noticed that we have 10 brightness level and the difference between the graduations is pretty big and noticeable. Especially between the darkest and second darkest level. Having than 10 brightness level would be great. The Pandora has a lot. 50 I guess and the script decides how many graduations per button press the brightness is increased/decreased. I like that solution. Maybe one could increase the brihtness level and I'll adjust the script then.
BTW: 10 brightness level for the Keyboard are fine.
Best Wishes
Nino
Hi Nino,
Am 31.08.2017 um 08:44 schrieb Nino Bock askarus@openpandora.org:
Hello,
I did write a script to easily set the screen brightness. I noticed that we have 10 brightness level and the difference between the graduations is pretty big and noticeable. Especially between the darkest and second darkest level. Having than 10 brightness level would be great. The Pandora has a lot. 50 I guess and the script decides how many graduations per button press the brightness is increased/decreased. I like that solution. Maybe one could increase the brihtness level and I'll adjust the script then.
Can you try to compile your own device tree? This would allow you to work out a better definition of the steps.
Here is the definition of the backlight levels:
http://git.goldelico.com/?p=gta04-kernel.git;a=blob;f=arch/arm/boot/dts/pyra...
Basically it works as follows:
brightness-levels = <0 11 20 30 40 50 60 70 80 90 100>;
This means there are 10 levels above 0. So it is basically linear - but I don't remember where the "11" instead of 10 comes from. Maybe a typo nobody did notice so far...
Now psychophysics knows that the eye is a non-linear sensor for brightness. Therefore an exponentially growing curve could indeed fit better.
Maybe something like <0 1 2 3 5 10 20 33 50 100> or with more intermediate steps.
That would be the direction I would play with.
One thing not to forget is to define a default brightness level number.
BTW: 10 brightness level for the Keyboard are fine.
Fine!
BR, Nikolaus
On 31.08.2017 15:58, H. Nikolaus Schaller wrote:
Hi Nino,
Am 31.08.2017 um 08:44 schrieb Nino Bock askarus@openpandora.org:
Hello,
I did write a script to easily set the screen brightness. I noticed that we have 10 brightness level and the difference between the graduations is pretty big and noticeable. Especially between the darkest and second darkest level. Having than 10 brightness level would be great. The Pandora has a lot. 50 I guess and the script decides how many graduations per button press the brightness is increased/decreased. I like that solution. Maybe one could increase the brihtness level and I'll adjust the script then.
Can you try to compile your own device tree? This would allow you to work out a better definition of the steps.
I'll try. I know what the device tree is good for but never compiled one myself.
Here is the definition of the backlight levels:
http://git.goldelico.com/?p=gta04-kernel.git;a=blob;f=arch/arm/boot/dts/pyra...
Basically it works as follows:
brightness-levels = <0 11 20 30 40 50 60 70 80 90 100>;
This means there are 10 levels above 0. So it is basically linear - but I don't remember where the "11" instead of 10 comes from. Maybe a typo nobody did notice so far...
Now psychophysics knows that the eye is a non-linear sensor for brightness. Therefore an exponentially growing curve could indeed fit better.
Maybe something like <0 1 2 3 5 10 20 33 50 100> or with more intermediate steps.
That would be the direction I would play with.
One thing not to forget is to define a default brightness level number.
BTW: 10 brightness level for the Keyboard are fine.
Fine!
BR, Nikolaus
Am 01.09.2017 um 08:55 schrieb Nino Bock askarus@openpandora.org:
On 31.08.2017 15:58, H. Nikolaus Schaller wrote:
Hi Nino,
Am 31.08.2017 um 08:44 schrieb Nino Bock askarus@openpandora.org:
Hello,
I did write a script to easily set the screen brightness. I noticed that we have 10 brightness level and the difference between the graduations is pretty big and noticeable. Especially between the darkest and second darkest level. Having than 10 brightness level would be great. The Pandora has a lot. 50 I guess and the script decides how many graduations per button press the brightness is increased/decreased. I like that solution. Maybe one could increase the brihtness level and I'll adjust the script then.
Can you try to compile your own device tree? This would allow you to work out a better definition of the steps.
I'll try. I know what the device tree is good for but never compiled one myself.
It should be possible to do it in the Pyra like this (coarse and not tested principle):
apt-get install build-essentials apt-get install git git clone http://git.goldelico.com/gta04-kernel.git # or other repo git checkout <<branch>> modify arch/arm/boot/dts/pyra-mainboard-5.1.dtsi # or other files make letux_defconfig dtbs locate new dtb files in arch/arm/boot/dtb and copy to boot directory (ideally on a separate system on SD so you don't overwrite your working one)
Hi Nikolaus,
I think I finally sould come back to the display brightness graduation.
On 01.09.2017 09:50, H. Nikolaus Schaller wrote:
Am 01.09.2017 um 08:55 schrieb Nino Bock askarus@openpandora.org:
On 31.08.2017 15:58, H. Nikolaus Schaller wrote:
Hi Nino,
Am 31.08.2017 um 08:44 schrieb Nino Bock askarus@openpandora.org:
Hello,
I did write a script to easily set the screen brightness. I noticed that we have 10 brightness level and the difference between the graduations is pretty big and noticeable. Especially between the darkest and second darkest level. Having than 10 brightness level would be great. The Pandora has a lot. 50 I guess and the script decides how many graduations per button press the brightness is increased/decreased. I like that solution. Maybe one could increase the brihtness level and I'll adjust the script then.
Can you try to compile your own device tree? This would allow you to work out a better definition of the steps.
I'll try. I know what the device tree is good for but never compiled one myself.
It should be possible to do it in the Pyra like this (coarse and not tested principle):
apt-get install build-essentials apt-get install git git clone http://git.goldelico.com/gta04-kernel.git # or other repo git checkout <<branch>> modify arch/arm/boot/dts/pyra-mainboard-5.1.dtsi # or other files make letux_defconfig dtbs locate new dtb files in arch/arm/boot/dtb and copy to boot directory (ideally on a separate system on SD so you don't overwrite your working one)
It doesn't work for me. Doing "make letux_defconfig dtbs" does work but I don't have a arch/arm/boot/dtb folder. However I can find some dtb files in the /arch/arm/boot/dts folder. Putting them simply into the boot folder and reboot doesn't work. What else do I have to do? Do I need to recompile the whole Kernel?
Best Wishes
Nino
Hi Nino,
Am 06.10.2017 um 14:56 schrieb Nino Bock askarus@openpandora.org:
Hi Nikolaus,
I think I finally sould come back to the display brightness graduation.
On 01.09.2017 09:50, H. Nikolaus Schaller wrote:
Am 01.09.2017 um 08:55 schrieb Nino Bock askarus@openpandora.org:
On 31.08.2017 15:58, H. Nikolaus Schaller wrote:
Hi Nino,
Am 31.08.2017 um 08:44 schrieb Nino Bock askarus@openpandora.org:
Hello,
I did write a script to easily set the screen brightness. I noticed that we have 10 brightness level and the difference between the graduations is pretty big and noticeable. Especially between the darkest and second darkest level. Having than 10 brightness level would be great. The Pandora has a lot. 50 I guess and the script decides how many graduations per button press the brightness is increased/decreased. I like that solution. Maybe one could increase the brihtness level and I'll adjust the script then.
Can you try to compile your own device tree? This would allow you to work out a better definition of the steps.
I'll try. I know what the device tree is good for but never compiled one myself.
It should be possible to do it in the Pyra like this (coarse and not tested principle):
apt-get install build-essentials apt-get install git git clone http://git.goldelico.com/gta04-kernel.git # or other repo git checkout <<branch>> modify arch/arm/boot/dts/pyra-mainboard-5.1.dtsi # or other files make letux_defconfig dtbs locate new dtb files in arch/arm/boot/dtb and copy to boot directory (ideally on a separate system on SD so you don't overwrite your working one)
It doesn't work for me. Doing "make letux_defconfig dtbs" does work but I don't have a arch/arm/boot/dtb folder.
Oops. Did you git clone the kernel source tree?
You should see the dts folder like here:
http://git.goldelico.com/?p=gta04-kernel.git;a=tree;f=arch/arm/boot/dts;h=0b...
However I can find some dtb files in the /arch/arm/boot/dts folder. Putting them simply into the boot folder and reboot doesn't work. What else do I have to do? Do I need to recompile the whole Kernel?
No, only the dtb files.
BR, NIkolaus
Hi Nikolaus,
On 06.10.2017 22:03, H. Nikolaus Schaller wrote:
Hi Nino,
Am 06.10.2017 um 14:56 schrieb Nino Bock askarus@openpandora.org:
Hi Nikolaus,
I think I finally sould come back to the display brightness graduation.
On 01.09.2017 09:50, H. Nikolaus Schaller wrote:
Am 01.09.2017 um 08:55 schrieb Nino Bock askarus@openpandora.org:
On 31.08.2017 15:58, H. Nikolaus Schaller wrote:
Hi Nino,
Am 31.08.2017 um 08:44 schrieb Nino Bock askarus@openpandora.org:
Hello,
I did write a script to easily set the screen brightness. I noticed that we have 10 brightness level and the difference between the graduations is pretty big and noticeable. Especially between the darkest and second darkest level. Having than 10 brightness level would be great. The Pandora has a lot. 50 I guess and the script decides how many graduations per button press the brightness is increased/decreased. I like that solution. Maybe one could increase the brihtness level and I'll adjust the script then.
Can you try to compile your own device tree? This would allow you to work out a better definition of the steps.
I'll try. I know what the device tree is good for but never compiled one myself.
It should be possible to do it in the Pyra like this (coarse and not tested principle):
apt-get install build-essentials apt-get install git git clone http://git.goldelico.com/gta04-kernel.git # or other repo git checkout <<branch>> modify arch/arm/boot/dts/pyra-mainboard-5.1.dtsi # or other files make letux_defconfig dtbs locate new dtb files in arch/arm/boot/dtb and copy to boot directory (ideally on a separate system on SD so you don't overwrite your working one)
It doesn't work for me. Doing "make letux_defconfig dtbs" does work but I don't have a arch/arm/boot/dtb folder.
Oops. Did you git clone the kernel source tree?
You should see the dts folder like here:
http://git.goldelico.com/?p=gta04-kernel.git;a=tree;f=arch/arm/boot/dts;h=0b...
Yes, I did. I do have the dts folder. Simply when doing the make command the dtb files are not stored in a seperate directory but in the same folder as the dts and dtsi files.
However I can find some dtb files in the /arch/arm/boot/dts folder. Putting them simply into the boot folder and reboot doesn't work. What else do I have to do? Do I need to recompile the whole Kernel?
No, only the dtb files.
All of them or only the omap-whatever-pyra ones? I've tried all of them as well as only the pyra ones and don't get any results.
At least the brightness steps are the same when increasing brightness by 1.
BR, NIkolaus
Hi Nino,
Am 07.10.2017 um 08:49 schrieb Nino Bock askarus@openpandora.org:
Hi Nikolaus,
You should see the dts folder like here:
http://git.goldelico.com/?p=gta04-kernel.git;a=tree;f=arch/arm/boot/dts;h=0b...
Yes, I did. I do have the dts folder. Simply when doing the make command the dtb files are not stored in a seperate directory but in the same folder as the dts and dtsi files.
Yes, that is normal. Like .o files are in the same folder as the .c files.
However I can find some dtb files in the /arch/arm/boot/dts folder. Putting them simply into the boot folder and reboot doesn't work. What else do I have to do? Do I need to recompile the whole Kernel?
No, only the dtb files.
All of them or only the omap-whatever-pyra ones?
It should suffice to copy the omap*.dtb but itdoes not harm to copy all of them. U-Boo chooses one of them.
I've tried all of them as well as only the pyra ones and don't get any results.
At least the brightness steps are the same when increasing brightness by 1.
Hm. Then let's do a test: * make a backup of the arch/arm/boot/dts directory * modify the steps * make dtbs * diff the dts directory with the backup directory - then you will know that the compilation does a change (and to which files)
The next thing is to check the boot log from U-Boot. It tells which .dtb file is loaded. Then you can check if it is the one that you have really changed.
Next you can play to modify the "model" entry in the device tree source and check with cat /proc/device-tree/model if it is really modified when the Pyra has booted.
Another idea: install the fdttools package. There is fdtdump to inspect .dtb files.
Hope this helps, Nikolaus
Hi Nikolaus,
I apologies for not replaying for such a long time. After I did a complete reinstall of the Pyra OS I noticed there is a new /boot/dtb/linux-image-4.15.0-rc8-letux-lpae-pyra/ folder. So I tried again and this time the recompilation of the pyra-mainboard-v5.0dtsi was effective.
I tried different values for screen ad keyboard background brightness settings. Here's my result:
Screen: <0 5 7 10 12 14 17 20 25 30 35 40 50 65 80 100> Keyboard: <0 1 2 5 10 20 40 60 100>
Is it mandatory to have exactly or less then 10 steps? If we use more for the screen it feels better to me. For the Keyboard 9 steps are enough.
In my opinion 5 as minimum brightness for screen is ok. Below I wouldn't even use it in complete darkness. My eyes are very light sensitive and I'd say below 5 even I would consider it as not readable any more.
For the Keyboard there's not much difference between 60 and 100. But here 1 as minimum is good. It's still bright enough to read the buttons well in darkness but it's not disturbing. Even 5 as a minimum might be too much for light sensitive people. I wouldn't mind having 0.5 here though.
I've attached the file. Brightness graduation is the only change I've made.
Best Wishes Nino
On 07.10.2017 14:16, H. Nikolaus Schaller wrote:
Hi Nino,
Am 07.10.2017 um 08:49 schrieb Nino Bock askarus@openpandora.org:
Hi Nikolaus,
You should see the dts folder like here:
http://git.goldelico.com/?p=gta04-kernel.git;a=tree;f=arch/arm/boot/dts;h=0b...
Yes, I did. I do have the dts folder. Simply when doing the make command the dtb files are not stored in a seperate directory but in the same folder as the dts and dtsi files.
Yes, that is normal. Like .o files are in the same folder as the .c files.
However I can find some dtb files in the /arch/arm/boot/dts folder. Putting them simply into the boot folder and reboot doesn't work. What else do I have to do? Do I need to recompile the whole Kernel?
No, only the dtb files.
All of them or only the omap-whatever-pyra ones?
It should suffice to copy the omap*.dtb but itdoes not harm to copy all of them. U-Boo chooses one of them.
I've tried all of them as well as only the pyra ones and don't get any results.
At least the brightness steps are the same when increasing brightness by 1.
Hm. Then let's do a test:
- make a backup of the arch/arm/boot/dts directory
- modify the steps
- make dtbs
- diff the dts directory with the backup directory - then you will know that the compilation does a change (and to which files)
The next thing is to check the boot log from U-Boot. It tells which .dtb file is loaded. Then you can check if it is the one that you have really changed.
Next you can play to modify the "model" entry in the device tree source and check with cat /proc/device-tree/model if it is really modified when the Pyra has booted.
Another idea: install the fdttools package. There is fdtdump to inspect .dtb files.
Hope this helps, Nikolaus
Hi Nino,
Am 25.03.2018 um 21:54 schrieb Nino Bock askarus@openpandora.org:
Hi Nikolaus,
I apologies for not replaying for such a long time. After I did a complete reinstall of the Pyra OS I noticed there is a new /boot/dtb/linux-image-4.15.0-rc8-letux-lpae-pyra/ folder. So I tried again and this time the recompilation of the pyra-mainboard-v5.0dtsi was effective.
I tried different values for screen ad keyboard background brightness settings. Here's my result:
Screen: <0 5 7 10 12 14 17 20 25 30 35 40 50 65 80 100> Keyboard: <0 1 2 5 10 20 40 60 100>
Is it mandatory to have exactly or less then 10 steps?
No.
If we use more for the screen it feels better to me. For the Keyboard 9 steps are enough.
In my opinion 5 as minimum brightness for screen is ok. Below I wouldn't even use it in complete darkness. My eyes are very light sensitive and I'd say below 5 even I would consider it as not readable any more.
For the Keyboard there's not much difference between 60 and 100.
Maybe the DC/DC converter is in saturation.
But here 1 as minimum is good. It's still bright enough to read the buttons well in darkness but it's not disturbing. Even 5 as a minimum might be too much for light sensitive people. I wouldn't mind having 0.5 here though.
I've attached the file. Brightness graduation is the only change I've made.
Works fine!
So I have taken your changes and parts of your description to form a git commit that will be in the next letux-rc.
I have also changed the default brightness. And, I have - assuming that you are ok with it - a signed-off: for you.
Best Wishes Nino
BR and thanks, Nikolaus
On 07.10.2017 14:16, H. Nikolaus Schaller wrote:
Hi Nino,
Am 07.10.2017 um 08:49 schrieb Nino Bock askarus@openpandora.org:
Hi Nikolaus,
You should see the dts folder like here:
http://git.goldelico.com/?p=gta04-kernel.git;a=tree;f=arch/arm/boot/dts;h=0b...
Yes, I did. I do have the dts folder. Simply when doing the make command the dtb files are not stored in a seperate directory but in the same folder as the dts and dtsi files.
Yes, that is normal. Like .o files are in the same folder as the .c files.
However I can find some dtb files in the /arch/arm/boot/dts folder. Putting them simply into the boot folder and reboot doesn't work. What else do I have to do? Do I need to recompile the whole Kernel?
No, only the dtb files.
All of them or only the omap-whatever-pyra ones?
It should suffice to copy the omap*.dtb but itdoes not harm to copy all of them. U-Boo chooses one of them.
I've tried all of them as well as only the pyra ones and don't get any results.
At least the brightness steps are the same when increasing brightness by 1.
Hm. Then let's do a test:
- make a backup of the arch/arm/boot/dts directory
- modify the steps
- make dtbs
- diff the dts directory with the backup directory - then you will know that the compilation does a change (and to which files)
The next thing is to check the boot log from U-Boot. It tells which .dtb file is loaded. Then you can check if it is the one that you have really changed.
Next you can play to modify the "model" entry in the device tree source and check with cat /proc/device-tree/model if it is really modified when the Pyra has booted.
Another idea: install the fdttools package. There is fdtdump to inspect .dtb files.
Hope this helps, Nikolaus
<pyra-mainboard-v5.0.dtsi>
-
H. Nikolaus Schaller -
Nino Bock