On 2016-10-01, Rick Thomas wrote: > On Jun 5, 2016, at 1:35 PM, Vagrant Cascadian <vagrant@debian.org> wrote: >> On 2016-06-05, Gaudenz Steinlin wrote: >>> I have the same problem with my Cubox-i 4x4. Is there any progress on >>> this? ... >>> Are the patches incorporated into the latest version in experimental? >> >> No, it requires a patch that does run-time detection. At least the >> versions of u-boot in debian currently boot on both cubox-i4x4 and >> cubox-i4pro, even if it limits ram to 2gb on the i4x4. >> >> >>> Is there anything I could test to get this into Debian? >> >> Someone could write a patch acceptible for u-boot upstream that does >> run-time detection... there may be folks on #u-boot on irc.freenode.net >> willing to help a bit. >> >> It also might be good to file a bug report against the u-boot-imx >> package in Debian at this point, so that the issue can at least be >> tracked appropriately. ... > Sorry to bring this back up after such a long time, but I had a couple > of thoughts that I’d like to bounce off those more knowledgable than > I. > > Would it be possible to do one or the other of these two: > > 1) Put the 2GB vs 4GB setting in the .dtb file. > > 2) Put setting in a kernel command line argument. I believe it actually requires u-boot to initialize ram timings and various other parameters. You can trick the kernel into using more memory, but in my experience that just caused crashes when trying to use more ram than u-boot initilized. It would of course be useful to experiment with alternative methods, but my guess is getting proper patches into u-boot may likely be the simplest approach. It just takes some work. live well, vagrant
Attachment:
signature.asc
Description: PGP signature