Hi,
the mentioned PR included a few new packages. I don't know the layerscape
platform, so I just want to understand it: these packages are all
necessary to
boot a "reasonable"
system? And this is true for fmc, too?
[Y.b. Lu] fmc is an important userspace tool for layerscape which is
Hi,
the mentioned PR included a few new packages. I don't know the layerscape
platform,
so I just want to understand it: these packages are all necessary to boot a
"reasonable"
system? And this is true for fmc, too?
Then one option would be to move libxml2 to "core openwrt".
If not, it would
Am Freitag, 30. März 2018, 18:03:19 CEST schrieb Yousong Zhou:
> On 30 March 2018 at 17:53, Koen Vandeputte
> wrote:
> > A lot of scripts are not set executable and thus will not run on invocation.
> > Fix this by setting appropriate rights.
> >
> > Currently, only
e complete OpenSSL 1.1
> +interface.
> +
> +Signed-off-by: Hauke Mehrtens <ha...@hauke-m.de>
> +---
> + tools/mxsimage.c | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +--- a/tools/mxsimage.c
> b/tools/mxsimage.c
> +@@ -26,7 +26,7 @@
> + * OpenSSL 1.1.
Hi,
Am Donnerstag, 22. Februar 2018, 17:48:58 CET schrieb Rosen Penev:
> Currently, the build system uses an openwrt mirror which does not currently
> workand FTP can be unreliable under several circumstances (Ubuntu 16.04 WSL
> being an example). This change implicitly allows using all the
Hi,
Am Sonntag, 18. Februar 2018, 22:43:42 CET schrieb Hauke Mehrtens:
> ...
>
> The following targets are on kernel 4.9 and are fine:
> ...
> * mxs
> ...
a few weeks ago, I was in contact with Zoltan who started working
on 4.14 support for mxs. I found some patches in his staging repo
and
:(.text+0x24ef): undefined reference to `EVP_CIPHER_CTX_reset'
mxsimage.c:(.text+0x2e52): undefined reference to `EVP_MD_CTX_free'
collect2: error: ld returned 1 exit status
Signed-off-by: Michael Heimpold <m...@heimpold.de>
---
package/boot/uboot-mxs/Makefile | 2 +-
1 file changed, 1 ins
Also update the U-Boot BSP patch for I2SE Duckbill devices.
Signed-off-by: Michael Heimpold <m...@heimpold.de>
---
package/boot/uboot-mxs/Makefile| 4 +-
.../uboot-mxs/patches/001-add-i2se-duckbill.patch | 408 +++--
2 files changed, 292 insertions(+
The Device Tree file for I2SE Duckbill boards was updated upstream.
Let's use the upstream version for upcoming kernel 4.14 by keeping
our current version for v4.9 still around.
Signed-off-by: Michael Heimpold <m...@heimpold.de>
---
.../linux/mxs/{files => files-4.9}/arch/arm/boot/
Hi,
> ...
> +CONFIG_EXT2_FS=y
> +CONFIG_EXT2_FS_POSIX_ACL=y
> +CONFIG_EXT2_FS_SECURITY=y
> +CONFIG_EXT2_FS_XATTR=y
> +CONFIG_EXT3_FS=y
> +CONFIG_EXT3_FS_POSIX_ACL=y
> +CONFIG_EXT3_FS_SECURITY=y
is this really necesarry? I thought that ext4 will handle this smoothly...
Regards,
Michael
not also directly
mention the SSL/TLS packages with a pattern. That will save one step
next time when stumbling here - at least for me ;-)
Signed-off-by: Michael Heimpold <m...@heimpold.de>
---
uclient-fetch.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/uclient-fetch.c b/u
Hi John,
Am Montag, 1. Januar 2018, 12:12:35 CET schrieb John Crispin:
>
> On 21/12/17 23:59, Michael Heimpold wrote:
> > At the moment, the image file operated on is always truncated
> > to 512 bytes. This limits the usage of ptgen somewhat.
>
> O_TRUNC truncates t
bootloader partition
within the first erase block on an eMMC, but then aligning the rootfs to
next start of erase block.
This change splits the global alignment parameter to individual ones
which thus allows individual partition alignment.
Signed-off-by: Michael Heimpold <m...@heimpold.de>
---
Signed-off-by: Michael Heimpold <m...@heimpold.de>
---
tools/firmware-utils/src/ptgen.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/tools/firmware-utils/src/ptgen.c b/tools/firmware-utils/src/ptgen.c
index b5e317d..af14d73 100644
--- a/tools/firmware-uti
Signed-off-by: Michael Heimpold <m...@heimpold.de>
---
tools/firmware-utils/src/ptgen.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/tools/firmware-utils/src/ptgen.c b/tools/firmware-utils/src/ptgen.c
index ff97cd5..b5e317d 100644
--- a/tools/firmware-uti
-off-by: Michael Heimpold <m...@heimpold.de>
---
tools/firmware-utils/src/ptgen.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/firmware-utils/src/ptgen.c b/tools/firmware-utils/src/ptgen.c
index 93d66eb..ff97cd5 100644
--- a/tools/firmware-utils/src/ptgen.c
+++ b
Signed-off-by: Michael Heimpold <m...@heimpold.de>
---
tools/firmware-utils/src/ptgen.c | 60 +++-
1 file changed, 34 insertions(+), 26 deletions(-)
diff --git a/tools/firmware-utils/src/ptgen.c b/tools/firmware-utils/src/ptgen.c
index 8466d35..93d66eb
for details.
This series is also available at GitHub:
https://github.com/mhei/source/commits/ptgen-fixes
Michael Heimpold (7):
firmware-tools/ptgen: fix minor coding style issues
firmware-tools/ptgen: do not truncate the output file
firmware-tools/ptgen: use portable exit codes
firmware-tools
6144 3M 83 Linux
test2.img2 8192270335262144128M 83 Linux
test2.img3 270336532479262144128M 83 Linux
Free space 532480 2097151 1564672764M
Signed-off-by: Michael Heimpold <m...@heimpold
Signed-off-by: Michael Heimpold <m...@heimpold.de>
---
tools/firmware-utils/src/ptgen.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/tools/firmware-utils/src/ptgen.c b/tools/firmware-utils/src/ptgen.c
index af14d73..3e1b8ba 100644
--- a/tools/firmware-uti
Hi,
according to my installed man page, %m is a Glibc extension.
It seems that musl also supports it, but should/can we assume
it for every C library? I have external toolchains in mind...
Not an objection, just a question :-)
mhei
___
Lede-dev
Hi Philip,
Am Dienstag, 25. Juli 2017, 10:29:06 CEST schrieb Philip Prindeville:
> I’m working on Issue #4588 (ntpd needs UCI parsing comparable to sysntpd)
> and I had a question…
>
> ntpd ships with the canned /etc/ntp.conf from the distro, but if we specify:
>
>
> config timeserver ntp
>
I2SE Duckbill devices and Olimex Olinuxino Maxi boards successfully [1].
Signed-off-by: Michael Heimpold <m...@heimpold.de>
[1] Tested:
- debug uart is working
- boot without any obvious kernel problem
- network is coming up and data transfer is possible
- Olinuxino: USB detects a plugged-
In preparation for bumping mxs target to 4.9, disable a bunch of configuration
symbols that provoked config prompts.
Signed-off-by: Michael Heimpold <m...@heimpold.de>
---
target/linux/generic/config-4.9 | 4
1 file changed, 4 insertions(+)
diff --git a/target/linux/generic/config
Commit 29443e2 (mxs: remove modules.mk, select drivers in the kernel config)
missed to remove these references, so cleanup it now.
Signed-off-by: Michael Heimpold <m...@heimpold.de>
---
target/linux/mxs/Makefile | 2 --
target/linux/mxs/profiles/01-duckbill.mk
RVED_PCT symbol available since it is bound to
> TARGET_ROOTFS_EXT4FS.
thanks for clarification, I think I got the idea.
So, feel free to add optionally:
Reviewed-by: Michael Heimpold <m...@heimpold.de>
Regards,
mhei
>
> In any case the change will neither alter current behav
IZE) \
> - -i $(CONFIG_TARGET_EXT4_MAXINODE) \
> $(if $(CONFIG_TARGET_EXT4_RESERVED_PCT),-m
> $(CONFIG_TARGET_EXT4_RESERVED_PCT)) \ $(if
> $(CONFIG_TARGET_EXT4_JOURNAL),,-J) \
> $(if $(SOURCE_DATE_EPOCH),-T $(SOURCE_DATE_EPOCH)) \
Acked-by: Mic
Hi Jo-Philipp,
sorry, I did not notice this in the last review, but how is it
possible to let CONFIG_TARGET_EXT4_RESERVED_PCT be empty?
config/Config-images.in:
config TARGET_EXT4_RESERVED_PCT
int "Percentage of reserved blocks in root filesystem"
depends on TARGET_ROOTFS_EXT4FS
default 0
Hi,
Am Montag, 17. Oktober 2016, 22:08:06 CEST schrieb Jo-Philipp Wich:
> Hi Michael,
>
> > I can't see why adjusting the default partition size would have been
> > necessary
> > as genext2fs takes (or better: took) the following parameters:
> The filesystem is generated okay but due to the
Hi,
Am Sonntag, 16. Oktober 2016, 01:59:44 CEST schrieb Jo-Philipp Wich:
> Commit fe20272ab16068765a191f3a846f30f977bc7669 (SVN r40924) introduced
> support for specifying ext4 blocksizes but silently switched the implicit
> 1K value to 4K by default without also adjusting the default partition
Hi,
Am Sonntag, 16. Oktober 2016, 01:59:43 CEST schrieb Jo-Philipp Wich:
> There is very little practical use to limit the number of available inodes
> on an ext4 filesystem and the make_ext4fs utility is able to calculate
> useful defaults by itself.
>
> Keep the option
I always wondered
31 matches
Mail list logo