Kristian Evensen <kristian.even...@gmail.com> [2019-05-04 12:07:33]: Hi,
> On Fri, May 3, 2019 at 6:32 PM Petr Štetiar <yn...@true.cz> wrote: > > > In order to install OpenWRT, you first need to compile an initramfs > > > (ramdisk)-image for the device. > > > > if the ramdisk image is needed, then we probably should enable it for that > > target and provide it, we shouldn't demand end users to build the ramdisk > > images by themselves in order to be able to install OpenWrt, right? > > > > This needs adding `ramdisk` in FEATURES in target.mk. > > I agree, building a ramdisk-image by default would be preferable. > However, wont adding ramdisk to FEATURES build a ramdisk image for all > mt7620-boards? Do you know any way to avoid that? Unfortunately no, but I've just proposed[1] some temporary workaround, so let's see how this pans out. Until it's accepted, I would simply go with that proposed `FEATURES += ramdisk` based solution. 1. http://lists.infradead.org/pipermail/openwrt-devel/2019-May/016931.html > > > +&pinctrl { > > > + state_default: pinctrl0 { > > > + default { > > > + ralink,group = "i2c", "uartf", "pa", "spi refclk", > > > "wled"; > > > + ralink,function = "gpio"; > > > + }; > > > + }; > > > +}; > > > > ... > > I have to admit that I don't understand what you are refering to there > (unless it is the too long "ralink,group"-line) :) It's just a poor-man's replacement for a picture of scissors, meaning, that I've simply removed some text around this `...` line. BTW, I haven't had time to check correctness of this pinctrl yet, but I'll do so. -- ynezz _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
