| 11:10 | warped-rudi> | Hi there! Where can I find a tool to test KMS i.e. list and switch modes? |
| 12:51 | Ke> | if I want ton configure u-boot env, what do I need to do on u-boot marvell |
| 12:51 | Ke> | -n |
| 12:51 | Ke> | it seems SPL_ENV is the thing, but SPL seems to be for other SoCs mainly |
| 12:52 | Ke> | or is ENV embedded into the bootloader image, if I don't set the SPL |
| 13:17 | jnettlet[m]> | Ke: just use env save to save your current environment. saveenv is broken in Marvell's u-boot |
| 13:18 | Ke> | jnettlet[m]: but how do I configure where it's stored in the u-boot build |
| 13:18 | Ke> | seems to be SPL stuff and SPL seems to be to some other platforms? |
| 13:18 | jnettlet[m]> | Ke: by default it is stored on the medium that it booted u-boot from |
| 13:18 | Ke> | inline in the bootloader image |
| 13:19 | Ke> | eg somewhere between the 2M start and 34M stop |
| 13:19 | Ke> | ? |
| 13:20 | jnettlet[m]> | oh, that may not work with the Marvell images because of they changes they have made to the environment logic. |
| 13:20 | Ke> | well I guess I can just try and see, what happens |
| 13:20 | jnettlet[m]> | they have overriden the default behaviour to store the env immediately after the u-boot.img |
| 13:21 | Ke> | so still somewhere within 2M...34M? |
| 13:21 | jnettlet[m]> | which you need to take into account because if you make changes and the image grows larger than the aligned size it will overwrite the env on the device |
| 13:21 | Ke> | or at 34M |
| 13:21 | jnettlet[m]> | it should be in < 2M |
| 13:22 | jnettlet[m]> | before the first partition |
| 13:24 | Ke> | ack |
| 13:26 | jnettlet[m]> | Ke: you will also be happy to know last week when I got down to the office one of the topics |