On Thursday, 9 May 2019 13:50:39 CEST Adrian Schmutzler wrote:
> diff --git a/target/linux/ath79/dts/qca9558_openmesh_om5p-ac-v2.dts b/
target/linux/ath79/dts/qca9558_openmesh_om5p-ac-v2.dts
> index 1e3cf40f71..fa74cf2344 100644
> --- a/target/linux/ath79/dts/qca9558_openmesh_om5p-ac-v2.dts
> +++ b
On 5/9/19 7:28 PM, Tomasz Maciej Nowak wrote:
Hi Jeff,
W dniu 09.05.2019 o 18:25, Jeff Kletsky pisze:
On 5/9/19 12:04 PM, Petr Štetiar wrote:
Jeff Kletsky [2019-05-09 11:23:18]:
I reconfirmed that
openwrt/target/linux/ath79$ cp generic/config-default nand/config-default
openwrt$
Hi Jeff,
W dniu 09.05.2019 o 18:25, Jeff Kletsky pisze:
> On 5/9/19 12:04 PM, Petr Štetiar wrote:
>
>> Jeff Kletsky [2019-05-09 11:23:18]:
>>
>>> I reconfirmed that
>>>
>>> openwrt/target/linux/ath79$ cp generic/config-default nand/config-default
>>> openwrt$ cat /dev/null > .config
>>>
On 5/9/19 12:04 PM, Petr Štetiar wrote:
Jeff Kletsky [2019-05-09 11:23:18]:
I reconfirmed that
openwrt/target/linux/ath79$ cp generic/config-default nand/config-default
openwrt$ cat /dev/null > .config
openwrt$ make menuconfig
has the same behavior -- the nand target does not set P
The factory firmware omits the JFFS2 end-marker while flashing via
web-interface. Add a 64k padding after the marker fixes this problem.
When the end-marker is not present, OpenWRT won't save the overlayfs
after initial flash.
Reported-by: Andreas Ziegler
Signed-off-by: David Bauer
---
target/
Here are recent release notes:
wave-1:
* April 2, 2019: Support some get/set API for eeprom rate power tables.
Mostly
backported from 10.2
* April 2, 2019: Support adaptive-CCA, backported from 10.2
* April 3, 2019: Support adding eeprom configAddr pairs v
This patch updates ath10k-ct to current version.
Changes are:
ath10k-ct: Fix printing PN in peer stats.
Previous logic was incorrect. Also add set-special API to enable
returning PN.
Patches refreshed and tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko
Add some read-only properties to protect partitions from
accidental changes.
Also fixed two whitespaces error on the way.
Signed-off-by: Adrian Schmutzler
---
Changes in v2:
- Do not change read-only for u-boot-env partitions
---
target/linux/ath79/dts/ar7241_ubnt_airrouter.dts | 4 ++--
W dniu 08.05.2019 o 20:40, Klaus Kudielka pisze:
> Recently, upgrade device autodetection has been added to the mvebu target.
> This exposes some shortcomings of the generic export_bootdevice function,
> e.g. on the Turris Omnia: export_bootdevice silently reports the root
> partition to be the boo
This series drops unnecessary cruft and improves image code, so that
it's better aligned with most well maintained targets in OpenWrt.
Additionally it introduces image for three ESPRESSObin variants.
Series is applicable after "mvebu: fix board_name condition in
79_move_config" by Klaus Kudielka.
Add vendors in device names and also rename few device names, for easier
identyfying potential firmware to flash. The vendor and device string is
mainly derived from model/compatipble string in dts from particular
device, but since not all devices are well described, some of the renames
follow mark
Convert whole target to Device Tree based board detection instead of
identifying devices by dts file name. With this we can drop mvebu.sh
translation script and rely on common method for model detection.
Signed-off-by: Tomasz Maciej Nowak
---
.../mvebu/base-files/etc/board.d/01_leds | 22 ++
This commit adds support for different iterations of ESPRESSObin.
The added variants are:
ESPRESSObin with soldered eMMC,
ESPRESSObin V7, compared to V5 some passive elements changed and ethernet
ports labels positions have been reversed,
ESPRESSObin V7 with soldered eMMC.
Please refer to:
584d
Use make syntax to pass the U-Boot image location and boot with root
partitions size, instead of relying on shell functions and variables.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/Makefile | 18 ++
.../linux/mvebu/image/gen_mvebu_sdcard_img.sh
All of arm64 devices have part of variables repeatedly defined. Stack
them to common define, and reference it in each device recipe.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/Makefile | 8
target/linux/mvebu/image/cortex-a53.mk | 12 ++--
target/linux
All of U-Boot scripts repeat the same pattern with only Device Tree blob
name changing for respective device. Therefore create generic scripts
which will be altered on demad by image build process, and create
BOOT_SCRIPT variable which can be added to device recipe and will allow
referencing the sa
Even if dts is not included in upstream Makefile, it is built anyway by
recipe specified in include/image.mk. Also remove Build/dtb, it's not
used since 3f72f3a ("mvebu: clearfog: include DTB for all variants in
image").
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/Makefile
Drop overly complex amount of defines wich are referenced in the same
devices pool and move image recipes to common define, since devices not
using them overwrite it.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/Makefile | 21 ---
target/linux/mvebu/image/corte
Adrian Schmutzler [2019-05-09 14:52:11]:
> > as ath79 has `DEFAULT_PACKAGES += uboot-envtools` and just few devices set
> > `DEFAULT_PACKAGES -= uboot-envtools` I would assume, that it's expected to
> > be
> > writeable.
>
> Okay. I also found some devices where u-boot-env IS read-only, e.g.
> h
Hi,
> -Original Message-
> From: Petr Štetiar [mailto:yn...@true.cz]
> Sent: Donnerstag, 9. Mai 2019 14:42
> To: Adrian Schmutzler
> Cc: openwrt-devel@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] [PATCH] ath79: Add missing read-only properties
>
> Adrian Schmutzler [2019-05-09 13:50
Adrian Schmutzler [2019-05-09 13:50:39]:
Hi,
> The read-only properties for non-firmware partitions seem to have been
> assigned rather randomly.
Instead of randomly I would say, that it was developer/submitter preference.
> label = "u-boot-env";
> +
The read-only properties for non-firmware partitions seem to have
been assigned rather randomly.
I went through the DTS files in ath79 and assigned the read-only
to all partitions that seem to require protection.
Also fixed a whitespace error on the way.
Signed-off-by: Adrian Schmutzler
---
tar
Jeff Kletsky [2019-05-09 11:23:18]:
> I reconfirmed that
>
> openwrt/target/linux/ath79$ cp generic/config-default nand/config-default
> openwrt$ cat /dev/null > .config
> openwrt$ make menuconfig
>
> has the same behavior -- the nand target does not set PCI_SUPPORT
it works here(tm):
On 5/9/19 10:49 AM, Robert Marko wrote:
I don't see any differences between the generic and nand subtargets'
`config-default`, `target.mk`, or `image/*.mk` that seem related to
PCI_SUPPORT.
Well, generic target has PCI symbols enabled in config-default
https://github.com/openwrt/openwrt/blob/ma
> I don't see any differences between the generic and nand subtargets'
> `config-default`, `target.mk`, or `image/*.mk` that seem related to
> PCI_SUPPORT.
Well, generic target has PCI symbols enabled in config-default
https://github.com/openwrt/openwrt/blob/master/target/linux/ath79/generic/confi
Jeff Kletsky [2019-05-09 10:29:31]:
Hi,
> I'm having some challenges understanding why PCI_SUPPORT is being set
> for the "generic" target, but not being set for the "nand" subtarget.
perhaps because nobody is using this nand subtarget, so nobody has noticed and
fixed it yet.
-- ynezz
___
Stijn Segers [2019-05-08 20:38:09]:
Hi,
> Op maandag 6 mei 2019 om 12:13 schreef Petr Štetiar :
> > Commit "lantiq/xrx200: enable initramfs images" enabled creation of
> > initramfs images for all devices in lantiq's xrx200 subtarget, just
> > because FRITZ7362SL needs initramfs during OpenWrt i
I'm having some challenges understanding why PCI_SUPPORT is being set
for the "generic" target, but not being set for the "nand" subtarget.
This seems to be the cause for the ath10k drivers not being available
in menuconfig.
While this has become an issue with the first port of an ath79 device
us
28 matches
Mail list logo
