**** BEGIN LOGGING AT Sat Sep 22 03:00:00 2018
Sep 22 09:50:20 <ldir> Hauke: I'll keep an eye out for the backport going through and remove our 'disable vdso' patch for 4.4/4.9 as required.....if Koen doesn't beat me to it....he's damn quick you know ;-)
Sep 22 10:46:56 <danitool> Hi, I'm trying to install Openwrt on the nand of this mvebu board https://openwrt.org/toh/buffalo/ls421de
Sep 22 10:47:10 <danitool> however uboot has bootargs hardcoded, is there any way to avoid passing uboot bootargs to the kernel without touching the kernel config?
Sep 22 10:48:53 <danitool> an this way force the kernel to use bootargs in the dts file
Sep 22 11:25:49 <DonkeyHotei> danitool: "chosen"
Sep 22 11:26:06 <danitool> chosen?
Sep 22 11:26:18 <DonkeyHotei> in dts
Sep 22 11:28:56 <danitool> DonkeyHotei: I already use chosen in dts, but the kernel overwrites bootargs with the one passed by uboot
Sep 22 11:30:09 <DonkeyHotei> so chosen is completely ignored?
Sep 22 11:31:10 <danitool> yes, unless I manually boot the uimage without setting bootargs in uboot
Sep 22 11:31:55 <danitool> using lede 17.01
Sep 22 11:33:02 <DonkeyHotei> what if you just change bootargs?
Sep 22 11:33:13 <danitool> I cannot rid of bootargs in uboot, since it's hardcoded
Sep 22 11:33:22 <danitool> nor change it
Sep 22 11:33:53 <DonkeyHotei> setenv bootargs console=ttyS0
Sep 22 11:33:55 <danitool> only a few variables can be changed, like mac address, uboot IP and minor non executable variables
Sep 22 11:35:02 <DonkeyHotei> what happens when you try?
Sep 22 11:36:22 <danitool> well when I try to saveenv, It just writes a few variables
Sep 22 11:36:49 <DonkeyHotei> does it change for the current boot?
Sep 22 11:38:33 <danitool> i can setenv, but not saveenv, btw I didn't make deep tests with all variables
Sep 22 11:39:42 <DonkeyHotei> so you can setenv bootargs and the kernel is ok, but after reboot, you're back where you were?
Sep 22 11:40:16 <danitool> indeed
Sep 22 11:40:39 <DonkeyHotei> did you opkg install uboot-envtools?
Sep 22 11:41:42 <danitool> yes, and I made some change, but it seems uboot it's not catching the stored variables in the uboot env area
Sep 22 11:41:53 <DonkeyHotei> hmm
Sep 22 11:42:45 <danitool> definitely it seem's the uboot is a bit locked, maybe I could compile a 2nd stage bootloader, but sounds a bit complex
Sep 22 11:43:53 <danitool> I suppose changing the kernel configuration I will have my own bootargs from dts
Sep 22 11:44:16 <danitool> but won't be the way to achieve the official support
Sep 22 11:46:44 <DonkeyHotei> that's how most devices are supported though
Sep 22 11:49:34 <danitool> I'm newbie with mvebu, nand stuff and low knowldedge with uboot, I always worked with CFE, mips and nor flash chips
Sep 22 11:53:23 <danitool> btw the uboot env variables seems embedded into uboot binary in plain text, maybe I can directly edit the binary but I'm afraid of ruining the integrity of the binary
Sep 22 11:55:10 <DonkeyHotei> no need
Sep 22 11:56:49 <tmn505> danitool: maybe start fresh with current master, there You have 006-mvebu-Mangle-bootloader-s-kernel-arguments.patch, maybe it'll help.
Sep 22 11:57:34 <DonkeyHotei> pretty sure 18.06 has that too
Sep 22 11:57:50 <tmn505> yep
Sep 22 11:58:22 <danitool> oh, nice, thanks for the suggestion
Sep 22 12:00:11 <DonkeyHotei> why were you using 17.01?
Sep 22 12:44:08 <danitool> DonkeyHotei: just because I had the build root already downloaded and prepared
Sep 22 18:46:57 <mirko> why do we have two "prepare"-targets defined in /Makefile? Some make-magic or a bug?
**** ENDING LOGGING AT Sun Sep 23 02:59:59 2018