On 22/08/2019 02:59, Paul Spooren wrote:
Both targets miss a subtarget causing an image naming style which is
different from other all othe targets, even tho it already uses
`x/generic/` as subfolder as if the subtarget would exist.
This commit adds the Generic subtarget resulting in consistent
Hi John,
This commit adds the Generic subtarget resulting in consistent naming.
and
already uses `x/generic/` as subfolder as if the subtarget would exist.
I'm very much in favor of consistent names[0][1][2] as it reduces the
hassle when trying automate things, like building images via an
Hello All,
I am trying to implement DMVPN with OpenWRT. That requires multipoint GRE
tunnels. In case of the multipoint GRE tunnel, the remote endpoint/peer
address will be resolved dynamically using NHRPD protocol/daemon.
I have gone through the GRE documentation at the following link.
Hi,
> > > + DEVICE_MODEL := Mi router 3G v2
> >
> > Capitalize "router". Despite, use DEVICE_VARIANT, so:
> >
> > + DEVICE_MODEL := Mi Router 3G
> > + DEVICE_VARIANT := v2
> >
> > > + SUPPORTED_DEVICES += mir3gv2
> >
> > Drop this line.
>
> So apparently this "v2" is in fact an _officially_
Using pad-squashfs ensures that the root.squashfs is assigned sufficient
LEBs on UBI such that all reads of the rootfs succeed, in order to avoid
read failures and kernel panics.
This fixes one such kernel panic observed on Meraki MR24 where an
inopportune-sized unpadded root.squashfs occurred.
Normally, root.squashfs should not be padded for alignment purposes,
because particularly on NOR flash it is typically concatenated with
other objects, like the kernel and device tree. However, in some cases
we do want the root.squashfs to be padded, in particular when it is
written into a ubi
On Tue, 13 Aug 2019 at 20:25, Paul Fertser wrote:
> diff --git a/target/linux/ramips/dts/mt7621_xiaomi_mir3g-v2.dts
> b/target/linux/ramips/dts/mt7621_xiaomi_mir3g-v2.dts
> new file mode 100644
> index 00..a1963d0072
> --- /dev/null
> +++
Thank you for the reply.
On Thu, Aug 22, 2019 at 11:18:01AM +0200, m...@adrianschmutzler.de wrote:
> to the existing configuration of the "Xiaomi Mi Router 4A Gigabit
> Edition (R4AG/R4A Gigabit)" (without adding a new device).
There's also an issue of R4AG not present in upstream and I can't
Hey Rafał!
On Thu, Aug 22, 2019 at 01:02:03PM +0200, Rafał Miłecki wrote:
> On Tue, 13 Aug 2019 at 20:25, Paul Fertser wrote:
> > diff --git a/target/linux/ramips/dts/mt7621_xiaomi_mir3g-v2.dts
> > b/target/linux/ramips/dts/mt7621_xiaomi_mir3g-v2.dts
> > new file mode 100644
> > index
This sorts the device definitions in image/Makefile alphabetically
for each subtarget/block.
The order of blocks has not been touched.
Signed-off-by: Adrian Schmutzler
---
During updating lantiq to DEVICE_VENDOR/DEVICE_MODEL scheme, it
became obvious that there is almost no sorting left in
From: Thomas Langer
When CONFIG_BUILD_SUFFIX is enabled, the target-* folders in build_dir
and staging_dir have this suffix in the name, but not the
toolchain directories. When detecting the names for "arch" and "libc",
also accept the suffix and do not use it for the toolchain path.
On 22/08/2019 08:47, Paul Spooren wrote:
Hi John,
This commit adds the Generic subtarget resulting in consistent naming.
and
already uses `x/generic/` as subfolder as if the subtarget would exist.
I'm very much in favor of consistent names[0][1][2] as it reduces the
hassle when trying
On Sat, 17 Aug 2019 at 12:31, Jo-Philipp Wich wrote:
> > [...]
> > +
> > + blobmsg_for_each_attr(option, options, rem) {
> > + const char *prefix = "UPGRADE_OPT_";
> > + char *name = malloc(strlen(prefix) +
> > strlen(blobmsg_name(option)));
> > + char
thanks a lot for your work, and answer!!
Enrico
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Hi,
I believe the PCI-IDs of the devices in your device tree are wrong,
see below:
On Sun, Jul 21, 2019 at 07:43:51AM +0200, Birger Koblitz wrote:
> ramips: add Edimax RG21S
>
> SoC: MediaTek MT7621AT dual-core @ 880MHz
> RAM: 256M (Nanya NT5CC128M)
> FLASH:16MB (Macronix MX25L12835F)
This applies alphabetic sorting to devices in image/* files.
For certain cases, this patch deviates from strict sorting, e.g.
to ensure that v10 comes after v9.
While at it, fix an indent and remove some useless empty lines.
Signed-off-by: Adrian Schmutzler
---
It would be nice if this was
Hello,
try to use peeraddr '0.0.0.0'
Pagarbiai,
Simonas Tamošaitis
On 8/22/19 10:21 AM, pothuganti sridhar wrote:
Hello All,
I am trying to implement DMVPN with OpenWRT. That requires multipoint
GRE tunnels. In case of the multipoint GRE tunnel, the remote
endpoint/peer address will be
Hello all,
I use OpenWrt 19.07 on BT Home Hub 5A, but it seams ath10k-ct driver is
really unstable (it work only first 2-10 minutes). The ath10k driver
work without problem. Can somebody help me with this issue ?
OpenWrt 19.07-SNAPSHOT, r10323-7d300326ee
dmesg:
...
[
Hello.
This bug was fixed in the master branch.
Please try latest snapshot.
Best Regards,
Lukonin Kirill
чт, 22 авг. 2019 г. в 23:06, Yaroslav Petrov :
> Hello all,
>
>
> I use OpenWrt 19.07 on BT Home Hub 5A, but it seams ath10k-ct driver is
> really unstable (it work only first 2-10
When bumping to 4.19 the patch responsible for scaning flash for FIS
partition got left out. Without it devices with RedBoot bootloader using
automatic partitions detection in dts won't boot with the new kernel.
Fixes: 3771176 ("ath79: add support for linux 4.19")
Signed-off-by: Tomasz Maciej
This target enforces metadata check so add the necessary information. It
was previously removed because md5 sum check. When using these sysupgrade
images on ar71xx target the check would complain about them not matching.
Signed-off-by: Tomasz Maciej Nowak
---
Few fixes with common denominator being RedBoot bootloader, mostly
related to images generation. Some of these will need a cherry-pick to
19.07 branch - I'll prepare the patches if theese will be commited.
I would like to also put some focus on FS#2428 [1] bug, which will
disable sysupgrade for
There is md5 sum of whole image embedded in combined-image header which
is checked on sysupgrade. The check will fail for ath79 images which
may have embedded metadata. This is because metadata are appended after
the combined image is created. To allow smooth transition from ar71xx to
ath79, strip
The frequency was filled acording the information from datasheet for
particular chip (Winbond 25Q128BVFG). Unfortunately this led to
coruption and introduced bad blocks on the chip. Reducing the frequency
to commonly used in ath79, made the board more stable and no new bad
blocks were spoted.
On 22.08.19 00:11, John Crispin wrote:
On 22/08/2019 08:47, Paul Spooren wrote:
Hi John,
This commit adds the Generic subtarget resulting in consistent naming.
and
already uses `x/generic/` as subfolder as if the subtarget would exist.
I'm very much in favor of consistent
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Paul Spooren
> Sent: Donnerstag, 22. August 2019 21:07
> To: John Crispin ; openwrt-devel@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] [PATCH] ipqx0xx: add Generic subtarget
>
>
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Tomasz Maciej Nowak
> Sent: Donnerstag, 22. August 2019 20:59
> To: openwrt-devel@lists.openwrt.org
> Cc: Matt Merhar
> Subject: [OpenWrt-Devel] [PATCH 7/7] ath79: image:
Hi!
What about setting peeraddr to 0.0.0.0 ?
Kind regards,
André
Am 22.08.19 um 09:21 schrieb pothuganti sridhar:
> Hello All,
>
> I am trying to implement DMVPN with OpenWRT. That requires multipoint GRE
> tunnels. In case of the multipoint GRE tunnel, the remote endpoint/peer
> address
Because a bug in handling partial erase blocks in 4.19 kernel, using
sysupgrade images will hard brick devices that use RedBoot bootloader
and have "FIS directory" with "RedBoot config" on the same erase block.
Since flashing the devices from bootloader is safe, and to not cause a
situation where
During review it slipped by that these devices use combined-image which
should never be used for newly added ones. Therefore switch to
sysupgrade-tar generated images introduced in 8f6f260 ("ath79:
routerstation: prepare to use sysupgrade-tar format image"). The
sysupgrade accepts both images for
Now that the md5 check is fixed and metadata present, sysupgrade on
ar71xx will complain about device not being supported by the image.
Since the cause is not matching strings for supported devices add them
accordingly.
Signed-off-by: Tomasz Maciej Nowak
---
31 matches
Mail list logo
