[LEDE-DEV] ubi images with lantiq
Hello Lede-Team We have developed an own layout with the lantiq xrx200 soc. For now we are useing the openwrt 15.05 Branch. I have evaluated the lede tree on our board. After some try an error the system is now booting with lede but only with jffs2 support mtd layout openwrt with ubifs - uboot - uboot_env - kernel - ubi mtd lyout lede with jffs2 - uboot - uboot_env - fimware I have enabled to build an ubi based firmware, but the firmware is always an jffs2? Does lede decieded to standardize only have jffs2 support for alle arch targets? Who can i get ubifs support back on image generation?. Regards Flo ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] procd: instance_stop causes a call to instance_removepid via instance_exit, no need to do this already when the instance will be stopped.
Signed-off-by: Jurgen Van Ham--- service/instance.c |1 - 1 file changed, 1 deletion(-) diff --git a/service/instance.c b/service/instance.c index d7d1f82..8f7835a 100644 --- a/service/instance.c +++ b/service/instance.c @@ -541,7 +541,6 @@ instance_stop(struct service_instance *in) in->halt = true; in->restart = in->respawn = false; kill(in->proc.pid, SIGTERM); - instance_removepid(in); } static void -- 1.7.9.5 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] MT7621: 2 or 4 CPUs?
Thanks Daniel, I also found it in the datasheet: MIPS MT Application Specific Extension (ASE) - Support for 2 Virtual Processing Elements (VPEs) per CORE - One Thread Context (TC) per VPE Regards, Gaetano On Fri, Jul 15, 2016 at 11:07 AM, Daniel Gollewrote: > Hi Gaetano, > > On Fri, Jul 15, 2016 at 11:01:12AM +0200, Gaetano Catalli wrote: >> Hello, >> >> I'm a bit confused about the number of CPUs of MT7621 SoC. >> From the MT7621 datasheet: >> >> "The MT7621 router-on-a-chip includes a 880 MHz MIPS 1004Kc CPU dual-core >> ..." >> >> So why does /proc/cpuinfo show 4 cpus? > > MIPS MT is similar to Intel's HyperThreading on x86. > > https://imgtec.com/mips/architectures/multi-threading/ > > ... "MT can make a single processor core appear to an SMP operating > system like two separate cores." > > > Cheers > > Daniel > >> >> Regards. >> >> -- >> gaetano catalli >> >> ___ >> Lede-dev mailing list >> Lede-dev@lists.infradead.org >> http://lists.infradead.org/mailman/listinfo/lede-dev -- gaetano catalli ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] MT7621: 2 or 4 CPUs?
Hi Gaetano, On Fri, Jul 15, 2016 at 11:01:12AM +0200, Gaetano Catalli wrote: > Hello, > > I'm a bit confused about the number of CPUs of MT7621 SoC. > From the MT7621 datasheet: > > "The MT7621 router-on-a-chip includes a 880 MHz MIPS 1004Kc CPU dual-core ..." > > So why does /proc/cpuinfo show 4 cpus? MIPS MT is similar to Intel's HyperThreading on x86. https://imgtec.com/mips/architectures/multi-threading/ ... "MT can make a single processor core appear to an SMP operating system like two separate cores." Cheers Daniel > > Regards. > > -- > gaetano catalli > > ___ > Lede-dev mailing list > Lede-dev@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] MT7621: 2 or 4 CPUs?
Hello, I'm a bit confused about the number of CPUs of MT7621 SoC. >From the MT7621 datasheet: "The MT7621 router-on-a-chip includes a 880 MHz MIPS 1004Kc CPU dual-core ..." So why does /proc/cpuinfo show 4 cpus? Regards. -- gaetano catalli ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH v2 2/8] apm821xx: add support for the Cisco Meraki MR24
On 2016-07-14 23:09, Christian Lamparter wrote: > On Thursday, July 14, 2016 10:02:36 PM CEST Felix Fietkau wrote: >> On 2016-07-14 21:39, Christian Lamparter wrote: >> > This is mostly because with subtargets, it's possible to have different >> > kernel configs. >> > >> > MyBook Live is somewhat unique compared to the MR24 or the WNDR4700. It >> > has to >> > do without any flash (the 512Kb flash on the MBL only contains the >> > u-boot). >> > The target's boot and rootfs has to be located on the SATA drive, so the >> > MBL >> > needs to have the ext2/4 built-in to boot. (WD's u-boot requires the >> > bootfs >> > to be ext2. We could do without it, if we didn't care about sysupgrade). >> > >> > The problem with having a shared target for MR24 and WNDR4700 is that the >> > they >> > have different hard-coded addresses (CONFIG_PPC_EARLY_DEBUG_44x_PHYSLOW) >> > for >> > the early console. Other than that, there is AFICT no reason. >> > >> > So, what's the plan? Have a NAS and ROUTER subtarget? And forget about the >> > early >> > console? >> I don't think early console is worth having subtargets for. > Having individual kernel-configs for targets would solve this. Individual kernel-configs would again increase the number of build configurations, so that's not an option. >> And regarding router vs nas: how much flash does the router have? Can it >> handle the extra stuff that NAS devices need in their kernel config? > The WNDR4700's kernel's uimage can be max 2M. Currently a lzma'd uimage > is at 1.5M. ext4 built-in will add another 150k. dm and md OK, I guess it makes sense to have router/nas subtargets then. >> Having unnecessary extra subtargets wastes resources on snapshot builds >> and releases, so I want as few of them as possible. > I've looked into a shared subtarget. One problem that came up was with the > "ext4" [0], "ramdisk" [1], squashfs, nand features in the FEATURES list. > > [0] MR24 will now select the CONFIG_TARGET_ROOTFS_EXT4FS option by > default and generate a useless ext4 rootfs. (Default 48M) In the image building code, a Device/* section can override the filesystems that are built for the device, using the FILESYSTEMS variable. > Note: The WNDR4700 will also generate a ext4 image. However, since it > has the option for a HDD, a rootfs on the HDD is do-able with > some additional work (e.g.: cmdline). > > [1] MyBook Live will now generate useless ramdisk and squashfs images. ramdisk images might still be useful. - Felix ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev