Hi,
(Resent the email since HTML format email was rejected by mailing list...)
Has anyone seen below issue when LEDE started up. The system would hang when
created jffs2 area.
This issue occurred on QSPI flash on layerscape like ls1046ardb, but Nor flash
worked fine with same rootfs like ls1043
> On 17 Dec 2017, at 21:21, Hauke Mehrtens wrote:
>
> This patch made GCC produce broken code, remove it.
> In mp_cmp_d() function in th libtommath shipped with dropbear the
> following code was compiled wrong:
>
> /* compare based on magnitude */
> if (a->used > 1) {
> return 1;
> }
>
> In
On 12/17/2017 10:21 PM, Hauke Mehrtens wrote:
> This patch made GCC produce broken code, remove it.
> In mp_cmp_d() function in th libtommath shipped with dropbear the
> following code was compiled wrong:
>
> /* compare based on magnitude */
> if (a->used > 1) {
> return 1;
> }
>
> In the broke
This patch made GCC produce broken code, remove it.
In mp_cmp_d() function in th libtommath shipped with dropbear the
following code was compiled wrong:
/* compare based on magnitude */
if (a->used > 1) {
return 1;
}
In the broken ASM this part returned -1 like the previous return
statement did
This is needed for procd init script protection to work.
flock adds 4248 bytes to stripped busybox binary.
Signed-off-by: Roman Yeryomin
---
package/utils/busybox/Config-defaults.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/utils/busybox/Config-defaults.in
b/pa
> On 17 Dec 2017, at 17:22, Etienne Haarsma wrote:
>
> uint8_t *oob = ops->oobbuf;
> uint8_t *buf = ops->datbuf;
> -@@ -2662,7 +2697,7 @@ err_out:
> - static int panic_nand_write(struct mtd_info *mtd, loff_t to, size_t len,
> - size_t *retlen, const uint8_t *
Once installed fou kernel module allows you to use FOU (Foo over UDP)
and GUE (Generic UDP encapsulation) tunnel protocols.
To get ip fou command working you also need to install ip-full.
Signed-off-by: Filip Moc
---
Notes:
More info about FOU can be found here: https://lwn.net/Articles/614
Refreshed all patches.
Made the following patch for Mediatek and Oxnas compatible with kernel 4.4.106:
0072-mtd-backport-v4.7-0day-patches-from-Boris.patch
Compile-tested: ar71xx
Run-tested: ar71xx
Signed-off-by: Etienne Haarsma
---
include/kernel-version.mk | 4 +-
.
Hey,
I remember seeing some interest a while back in DPDK.
I started a port of DPDK for some experiment I wanted to do, but in
the meantime I stopped because of reasons.
Here's the current code so far:
https://github.com/commodo/packages/tree/dpdk/net/dpdk
It should build in the current master
Advantages:
- preserves existing partition layout on the sd-card.
Only the boot and rootfs partition will be overwritten.
Please note that sysupgrade will refuse to upgrade, if the existing
installation has an incompatible partition layout. Future changes
to the bootfs and/or rootfs partition
This patch adds the compatible string for the various RPIs from
4.14 upstream.
Note: The 4.14 upstream does not include the compute modules.
If the CM* would just house the SoC, it could in theory use the
"raw" chip compatible string. However, these CM boards also come
with RAM and eMMC. So they h
This patch converts all the raspberrypi images to utilize
the common metadata-based image verification.
Note: the CM1 and CM3 currently use the same "rpi-cm"
boardname.
Signed-off-by: Christian Lamparter
---
.../linux/brcm2708/base-files/lib/upgrade/platform.sh | 17 ++---
target/
Use the values populated by the generic board detect function. The
first compatible from the device tree source file will be the board
name in userspace. The model property from the device tree source file
will be the model name.
Change the board name where used in the userspace and drop the targe
This patch enables metadata-supported image verification
for all apm821xx supported devices. Since this method comes
with a built-in image verification tool (fwtool), the previous
image checks can be removed.
Signed-off-by: Mathias Kresin
Signed-off-by: Christian Lamparter
---
.../apm821xx/base
This patch converts all apm821xx devices to the device-tree
board-detection method. All instances of the legacy
boardnames (mbl,mr24,...) are converted to "vendor,device"
identifier.
The custom board-detection code in apm821xx.sh is removed as
it no longer serves any purpose.
Signed-off-by: Mathi
Meraki choose to use their product's codename as the main
compatible string. Mathias Kresin commented that this is
a poor choice as this will confuse the users and devs once
the device-tree compatible is used for board-detection and
possible the image name.
Signed-off-by: Christian Lamparter
---
This patch sets the BOARD_NAME variable on each affected
apm821xx device. The existing DEVICE_PROFILE and
DEVICE_NAME assignments are deprecated as they no longer
serve any purpose.
The BOARD_NAME variable is used by the sysupgrade-tar
method to specifiy a directory overwrite for the
sysupgrade-$d
This patch appends the "apm,bluestone" or "amcc,apollo3g"
machine compatible string to the current device tree source.
Please note that unlike other archs the PPC DT code does
not regard the machine's compatible string as a priority
list. This is explained in the kernel's usage-model.txt as follow
Currently, the device name handle does not include the
manufacturer. This can make it hard do differentiate
between products from different vendors that have the
same product name. As the handle is used to derive
the image name.
Signed-off-by: Christian Lamparter
---
target/linux/apm821xx/image/
Signed-off-by: Christian Lamparter
---
target/linux/apm821xx/base-files/etc/diag.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/apm821xx/base-files/etc/diag.sh
b/target/linux/apm821xx/base-files/etc/diag.sh
index e45f2a8522..26c035c6f3 100755
--- a/target/lin
This patch rename all the DT source files in order to
match upstream's "manufacturer-device.dts" format.
Please note that the DEVICE_DTB isn't changed. This is
because the u-boot of the MyBook Live defines the
fdt_file variable to be "apollo3g/apollo3g.dtb".
Signed-off-by: Christian Lamparter
--
The commit 87b668765e1
("image: when using the new image build code, gzip ext4 images by default")
forced that all targets that select the ext4 as the root filesystem
to always compress the generated rootfs. This is fine, but this method
doesn't not allow to append the metadata on a per-target bas
Hi Jo,
(not subscribed, trying to reply to your mail extracted from the archives)
> > In Debian there were/are gcc-4.2 .. gcc-4.9, gcc-5 .. gcc-7.
> > And what about beauties like 'x86_64-linux-gnu-gcc-7'?
> > Why not ditch the 'gcc* --version' invocations and have people use
> > 'CC=fancy-named
23 matches
Mail list logo
