From: Michael Marley
This supports the Intel TCO Watchdog Timer Device, which has been
nearly ubiquitous in Intel chipsets for almost 20 years.
Signed-off-by: Michael Marley
---
package/kernel/linux/modules/other.mk | 15 +++
1 file changed, 15 insertions(+)
diff --git a/package
From: Michael Marley
The x86_64 build already has the k10temp driver for AMD processors
built in, so this patch adds the coretemp driver for the same
functionality on Intel processors.
Signed-off-by: Michael Marley
---
target/linux/x86/64/config-default | 1 +
1 file changed, 1 insertion
From: Michael Marley
This driver supports CPU-specific idle features on recent Intel
processors. It does not conflict with the ACPI idle driver and
that driver will continue to be used for unsupported and non-Intel
processors.
Signed-off-by: Michael Marley
---
target/linux/x86/64/config
From: Michael Marley
This driver supports the i2c controller on many Intel chipsets.
The patch also adds the i2c_smbus driver upon which i2c_i801
depends.
Signed-off-by: Michael Marley
---
package/kernel/linux/modules/i2c.mk | 30 ++
1 file changed, 30 insertions
ration and forcing it to be compiled into the kernel. Is that
also OK?
Michael
On 03/12/17 06:58, Felix Fietkau wrote:
> On 2017-03-11 23:48, mich...@michaelmarley.com wrote:
>> From: Michael Marley
>>
>> This driver supports the i2c controller on many Intel chipsets.
>&
I
haven't had a chance to look at what is causing it to build as a module
instead of into the kernel yet.
Michael
On 03/13/17 20:37, Philip Prindeville wrote:
Did you look at:
https://github.com/openwrt/openwrt/pull/326
it might be easier just to cherry-pick this in.
On Mar 11, 20
In preparation for bumping mxs target to 4.9, disable a bunch of configuration
symbols that provoked config prompts.
Signed-off-by: Michael Heimpold
---
target/linux/generic/config-4.9 | 4
1 file changed, 4 insertions(+)
diff --git a/target/linux/generic/config-4.9 b/target/linux/generic
I2SE Duckbill devices and Olimex Olinuxino Maxi boards successfully [1].
Signed-off-by: Michael Heimpold
[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 pen drive
---
target
ted, I've pushed it here:
https://github.com/mhei/packages/tree/ntpd-uci
I used the 'include' statement to have a mostly static /etc/ntp.conf
and generate a dynamic file for inclusion in /tmp...
HTH,
Michael
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@sandelman.ca http://www.sandelman.ca/| ruby on rails[
signature.asc
Description: PGP signature
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 maili
Signed-off-by: Michael Heimpold
---
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-utils/src/ptgen.c
+++ b/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
---
tools/firmware-utils
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
Signed-off-by: Michael Heimpold
---
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 100644
--- a/tools
-off-by: Michael Heimpold
---
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/tools/firmware-utils/src
Signed-off-by: Michael Heimpold
---
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-utils/src/ptgen.c
+++ b/tools
Signed-off-by: Michael Heimpold
---
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-utils/src/ptgen.c
+++ b/tools
small 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
---
tools/firmware-util
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 to 0
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
---
uclient-fetch.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/uclient-fetch.c b/uclient-fetch.c
index
gains in software :).
Depends upon whether there is hardware support for NAT,
which many devices have, wrapped up under NDAs.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
]
Laurent GUERBY wrote:
> On Sun, 2018-01-28 at 17:09 -0500, Michael Richardson wrote:
>> Laurent GUERBY wrote:
>> > I tested today a few things on a brand new TP-Link Archer C7
>> v4.0,
>> > LAN client Dell Latitude 74
bian stretch too.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@sandelman.ca http://www.sandelman.ca/| ruby o
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 smoot
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
---
.../linux/mxs/{files => files-4.9}/arch/arm/boot/dts/imx28-duckbill.dts
Also update the U-Boot BSP patch for I2SE Duckbill devices.
Signed-off-by: Michael Heimpold
---
package/boot/uboot-mxs/Makefile| 4 +-
.../uboot-mxs/patches/001-add-i2se-duckbill.patch | 408 +++--
2 files changed, 292 insertions(+), 120 deletions(-)
diff
b): undefined reference to `EVP_MD_CTX_free'
mxsimage.c:(.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
---
package/boot
s staging repo
and added some patches on top.
I've pushed this in a Github branch:
https://github.com/mhei/source/tree/mxs-4.14
I run tested this on both I2SE Duckbill devices and Olimex OLinuXino
Maxi boards - no obvious problems so far, so I think we can go ahead
for this platform with
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 mirr
> + 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.0 and newer compatibility functions:
> + * https://wiki.openssl.org/index.php/1.1_API_Changes
> +
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 files with extension .sh are ta
always wondered whether somebody really needs/uses this...
So, if nobody speaks up with a real use-case, I'd prefer to see
this option to go completely.
Regards,
Michael
> but make it empty by default to allow make_ext4fs to
> calculate the optimal number of inodes when generating an ext
ecause when you use the image on a real
device, e.g. eMMC or SD card, then usually the internal blocksize is 4k,
and internal erase block size is often even 4 MiB.
Thus using 1k blocksize is not optimal when using a writeable filesystem.
Regards,
Michael
>
> To support online resizing beyo
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
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
-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: Michael Heimpold
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
> + default 2048 if TARGET_x86
> + default 256 if ! TARGET_x86
> help
> Select the root filesystem partition size.
Acked-by: Michael Heimpold
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Hi Jo-Philipp,
Am Mittwoch, 26. Oktober 2016, 22:14:17 CEST schrieb Jo-Philipp Wich:
> Hi Michael,
>
> the line of thinking here was that the Image/mkfs/ext4 macro might get
> used in other target image build steps in which case there might not be
> CONFIG_TARGET_EXT4_RESE
ed SD Card,
changed the config files for RPI to boot from squashfs and specified
kernel and GO.
this process would be nice to automate via Makefiles if i choose
"squashfs" in .config File of the owrt-builder
(CONFIG_TARGET_ROOTFS_SQUASHFS=y)
regards
Michael
_
nice if we had a header that said "do not auto-learn this
address", too bad the IETF DMARC has been so slow.
It would be great if it could say instead:
LIST forward from First Last
which I admit won't sort as well.
--
] Never tell me the odds!
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
---
target/linux/mxs/Makefile | 2 --
target/linux/mxs/profiles/01-duckbill.mk| 3 +--
target/linux
istribute the public part only.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@sandelman.ca http://www.sandelman.ca/|
info/lede-dev
> ___ Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson,
Bastian Bittorf wrote:
> * Michael Richardson [23.02.2017 07:57]:
>> Yes, use an asymmetric key, and distribute the public part only.
> thanks people, for all the input and your ideas. our approach is now
> this: we hook into the 'usign' sourcecode and
Bastian Bittorf wrote:
> * Michael Richardson [24.02.2017 09:03]:
>> > large random primenumbers. On the serverside, we store the product >
>> (aka: solution) of these 2 numbers. This is repeated for each
>> generated > image. (sorry, it brea
Bastian Bittorf wrote:
> * Michael Richardson [24.02.2017 19:00]:
>> 2) call the first 16 bytes the build-identifier, base64 it. Or perhaps
>> bubble-babble it, and show it to the user, etc. as the recognizable
>> build name.
> the 'b
channel selection. Sucks...
Am I wrong in thinking that if you can lower your Tx power that you can bleed
less into adjacent channels?
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network
ld we avoid packages in the package feed which have a strong platform
dependency?
Just a few thoughts of mine,
Michael
Am Dienstag, 8. Mai 2018, 08:44:27 CEST schrieb Y.b. Lu:
> Hi John and Hauke,
>
> May I have your suggestion about an old problem? The pull request was merged
>
, this does not justify
to move PHP7 to core openwrt.
Don't get me wrong, I'm not a core developer and this are just
a few thoughts...
Michael
Fmc build and usage depends on several packages. They are tclap,
fmlib, and eth-config which I added in the PR. Both fmlib and
eth-confi
From: Michael Gray
Linksys WRT32X (Venom) is identical in hardware to the WRT3200ACM
with a different flash layout and boots zImage rather than uImage.
Specification:
- Marvell Armada 385 88F6820 (2x 1.8GHz)
- 256MB of Flash
- 512MB of RAM
- 2.4GHz (bgn) and 5GHz (an+ac wave 2)
- 4x 1Gbps LAN
>> +partition@0 {
>> +label = "u-boot";
>> +reg = <0x000 0x20>; /* 2MB */
>> +/* read-only; */
>> +};
>> +
>
>Why is the u-boot partition writable?
>
>
>Bjørn
Thanks
From: Michael Gray
Linksys WRT32X (Venom) is identical in hardware to the WRT3200ACM
with a different flash layout and boots zImage rather than uImage.
Specification:
- Marvell Armada 385 88F6820 (2x 1.8GHz)
- 256MB of Flash
- 512MB of RAM
- 2.4GHz (bgn) and 5GHz (an+ac wave 2)
- 4x 1Gbps LAN
I am trying to move from OpenWrt to LEDE. As a package maintainer, I often
build custom OpenWrt images, and I would like to do the same using
LEDE. However, I am having trouble installing what I build on a Mikrotik
RouterBoard 493G.
First, it appears the RouterBoard expects the kernel to exist wit
> Second, I am having trouble figuring out the right way to install the
> root filesystem. The best I have been able to figure out is:
>
> 1. Build a squashfs image.
>
> 2. Create ubi.conf:
>
> [root_volume]
> mode=ubi
> image=lede-ar71xx-mikrotik-root.squashf
I have been using OpenWrt to build HVM DomU guests under Xen for some
time. From what I can tell, Xen's PVHVM drivers (namely, netfront and
blkfront) are not available on my OpenWrt DomU guests, and thus the
guests rely on the slower QEMU-based drivers. As a result, the network
and disk performance
>> I have been using OpenWrt to build HVM DomU guests under Xen for some
>> time. From what I can tell, Xen's PVHVM drivers (namely, netfront and
>> blkfront) are not available on my OpenWrt DomU guests, and thus the
>> guests rely on the slower QEMU-based drivers. As a result, the network
>> and d
>From bc848f9f3d0ffb9aa114c7faa3916f059f5616b2 Mon Sep 17 00:00:00 2001
From: "W. Michael Petullo"
Date: Wed, 12 Jul 2017 07:02:18 -0400
Subject: [PATCH] block: support /dev/xvd* nodes
To: LEDE Development List
Xen provides paravirtualized block devices which most often appea
>> Xen provides paravirtualized block devices which most often appear as
>> /dev/xvd*. This patch adds this pattern to those known to the block
>> utilitiy. These devices require a kernel compiled with the xen-blkfront
>> driver.
> Having a closer look I just noticed that there are no XEN options
I am the maintainer of a number of OpenWrt packages, and I am watching
with interest the emargence of the LEDE project. Some time ago, OpenWrt
migrated to GitHub for some of its feeds, including the packages feed. At
that time, many of the packages were deprecated until the maintainter
manually mig
>> This should make x86-64 targets more useable out of the box.
>> The assumption is that most x86-64 users have adequate storage,
>> and those that do not can still config away the options they
>> do not need.
> Although I agree x86-64 is normally big, I'm not sure that it makes
> sense to make
Might it be possible to update the lua package in LEDE? There seems to
be an emerging problem with luasec and prosody and the current version
of lua. Luasec-0.6 requires lua-5.2 or lua-5.3, but LEDE and OpenWrt
provide only lua-5.1.
See also:
https://github.com/voidlinux/void-packages/is
n: ipq806x
Runtime-tested on: ipq806x
Tested-by: Michael Yartys
‐‐‐ Original Message ‐‐‐
On 7 May 2018 6:56 PM, Kevin Darbyshire-Bryant via Lede-dev
wrote:
> The sender domain has a DMARC Reject/Quarantine policy which disallows
>
> sending mailing list messages using the ori
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
The patch doesn't apply without ch
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
With the following reordering and
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
No issues.
Tested-b
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Tested-by: Mich
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Tested-by: Mich
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Tested-by: Mich
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Tested-by: Mich
al Message ‐‐‐
On 17 May 2018 3:56 PM, John Crispin wrote:
> On 17/05/18 13:47, Ram Chandra Jangir wrote:
>
> > Thanks Michael for confirming this,
> >
> > Can you please help to update the kernel partition size to 4MB for R7800
> > and send it as patch to
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Patch fails after since Lantiq h
72 matches
Mail list logo
