W dniu 15.06.2021 o 16:05, Koen Vandeputte pisze:
>
> On 13.06.21 18:28, Tomasz Maciej Nowak wrote:
>> Looking at OpenWrt downloading statistics this target has non-existent
>> userbase apart from me. Mark it as source-only to skip the build by
>> buildbots and not was
SoCs.
Ref: https://git.kernel.org/torvalds/c/cf9bf871280d
Signed-off-by: Tomasz Maciej Nowak
---
.../patches-5.10/700-mvneta-tx-queue-workaround.patch | 8 ++--
.../patches-5.4/700-mvneta-tx-queue-workaround.patch | 8 ++--
2 files changed, 12 insertions(+), 4 deletions(-)
diff
Hi,
one comment inline.
W dniu 14.08.2021 o 14:33, Jan-Niklas Burfeind pisze:
> The Onion Omega is a hardware development platform with built-in WiFi.
>
> https://onioniot.github.io/wiki/
>
> Specifications:
> - QCA9331 @ 400 MHz (MIPS 24Kc Big-Endian Processor)
> - 64MB of DDR2 RAM running at
W dniu 14.08.2021 o 16:37, Jan-Niklas Burfeind pisze:
> Hey there; answer is inline too.
> Thanks for picking this up!
>
> On 8/14/21 3:54 PM, Tomasz Maciej Nowak wrote:
>> Hi,
>> one comment inline.
>>
>> W dniu 14.08.2021 o 14:33, Jan-Niklas Burfeind pisze:
7;ve got the answer - the flash layout in device tree is then correct.
Yep, and thanks for chiming in. With that the MAC can be safely
extracted by nvmem.
Reviewed-by: Tomasz Maciej Nowak
Regards
--
TMN
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
This SBC has Microchip TCN75 sensor, wich measures ambient temperature.
Specify it in dts to allow readout by applications using kernel hwmon
API.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/ath79/dts/ar7161_jjplus_ja76pf2.dts | 13 +
target/linux/ath79/image/generic.mk
block erase size boundary.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/ath79/image/generic.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/ath79/image/generic.mk
b/target/linux/ath79/image/generic.mk
index 24bd12d652b6..bc078efad53e 100644
--- a/target/
Main changes revolve around changing the image format for devices which
share FIS directory and RedBoot config on same flash erase block and
cleanup following aftermath of this change.
Tomasz Maciej Nowak (7):
ath79: jj76pf2: enable TCN75 sensor
ath79: switch some RedBoot based divices to
Don't comence the switch to RAMFS when the image format is wrong. This
led to rebooting the device, which could lead to false impression that
upgrade succeded.
Being here, factor out the code responsible for upgrading RedBoot
devices to separate file.
Signed-off-by: Tomasz Maciej
fix) and rootfs image with firmware (firmware.bin
suffix).
Signed-off-by: Tomasz Maciej Nowak
---
.../linux/ath79/dts/ar7161_jjplus_ja76pf2.dts | 39 ++-
.../ath79/dts/ar7161_ubnt_routerstation.dtsi | 35 -
.../etc/uci-defaults/05_fix-compat-version| 5 ++-
-fis parser, the partition containig MAC adresses could be
specified, and with marking it as nvmem cell, we can assign them without
userspace involvement.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/ath79/dts/ar7161_jjplus_ja76pf2.dts | 15 +++
.../generic/base-files/etc
No reason to keep that around, since upstream one does the same.
Signed-off-by: Tomasz Maciej Nowak
---
.../ath79/dts/ar7161_adtran_bsap1880.dtsi | 2 +-
.../dts/bcm6348-inventel-livebox-1.dts| 2 +-
target/linux/gemini/image/Makefile| 4 ++--
...t-add-of_match_table
obsolete.
Signed-off-by: Tomasz Maciej Nowak
---
.../408-mtd-redboot_partition_scan.patch | 44 ---
1 file changed, 44 deletions(-)
delete mode 100644
target/linux/ath79/patches-5.10/408-mtd-redboot_partition_scan.patch
diff --git
a/target/linux/ath79/patches-5.10/408
Main changes revolve around changing the image format for devices which
share FIS directory and RedBoot config on same flash erase block and
cleanup following aftermath of this change.
Tomasz Maciej Nowak (7):
v1 -> v2
ath79: jj76pf2: enable TCN75 sensor
- none
ath79: switch some RedB
This SBC has Microchip TCN75 sensor, wich measures ambient temperature.
Specify it in dts to allow readout by applications using kernel hwmon
API.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/ath79/dts/ar7161_jjplus_ja76pf2.dts | 13 +
target/linux/ath79/image/generic.mk
-fis parser, the partition containig MAC adresses could be
specified, and with marking it as nvmem cell, we can assign them without
userspace involvement.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/ath79/dts/ar7161_jjplus_ja76pf2.dts | 15 +++
.../generic/base-files/etc
block erase size boundary.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/ath79/image/generic.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/ath79/image/generic.mk
b/target/linux/ath79/image/generic.mk
index 24bd12d652b6..bc078efad53e 100644
--- a/target/
Don't comence the switch to RAMFS when the image format is wrong. This
led to rebooting the device, which could lead to false impression that
upgrade succeded.
Being here, factor out the code responsible for upgrading RedBoot
devices to separate file.
Signed-off-by: Tomasz Maciej
fix) and rootfs image with firmware (firmware.bin
suffix).
Fixes: 15aa53d7ee65 ("ath79: switch to Kernel 5.10")
Signed-off-by: Tomasz Maciej Nowak
---
.../linux/ath79/dts/ar7161_jjplus_ja76pf2.dts | 39 ++-
.../ath79/dts/ar7161_ubnt_routerstation.dtsi | 35 ++
The redboot-fis parser has option to specify the location of FIS
directory, use that, instead of patching the parser to scan for it, and
specifying location in kernel config.
Tested-by: Brian Gonyer
Signed-off-by: Tomasz Maciej Nowak
---
.../ath79/dts/ar7161_adtran_bsap1880.dtsi | 1
No reason to keep that around, since upstream one does the same.
Signed-off-by: Tomasz Maciej Nowak
---
.../ath79/dts/ar7161_adtran_bsap1880.dtsi | 2 +-
.../dts/bcm6348-inventel-livebox-1.dts| 2 +-
target/linux/gemini/image/Makefile| 4 ++--
...t-add-of_match_table
All boards which include this dtsi have a power LED, which is by default
ON on running system, so there's no need to replicate it. Let the user
decide what to do with it on running system.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/ath79/dts/ar9344_mikrotik_routerboard.dtsi | 1
Most of boards from MikroTik with AR9344 SoC (supported and
un-supported) replicate the same schematic, so stack common device nodes
to a single dtsi.
Signed-off-by: Tomasz Maciej Nowak
---
.../ar9344_mikrotik_routerboard-16m-nor.dtsi | 8 -
.../ar9344_mikrotik_routerboard-lhg-5nd.dts
ut.
Known issues
Compared to ar71xx target image, there is still small leak of current to
user LED, which makes it lit, although weaker, even if brightness is set
to 0. The cause of that is still unknown.
Signed-off-by: Tomasz Maciej Nowak
---
.../ar9344_mikrotik_routerboard-911-lite
From: Tomasz Maciej Nowak
After the kernel has switched version to 5.10, JA76PF2 and
RouterStations lost the capability to sysupgrade the OpenWrt version.
The cause is the lack of porting the patches responsible for partial
flash erase block writing and these boards FIS directory and RedBoot
From: Tomasz Maciej Nowak
The bootloader on this board hid the partition containig MAC addresses
and prevented adding this space to FIS directory, therefore those had to
be stored in RedBoot configuration as aliases to be able to assigne them
to proper interfaces. Now that fixed partition size
From: Tomasz Maciej Nowak
Main changes revolve around changing the image format for devices which
share FIS directory and RedBoot config on same flash erase block and
cleanup following aftermath of this change.
Tomasz Maciej Nowak (7):
v2 -> v3
ath79: jj76pf2: enable TCN75 sensor
- n
From: Tomasz Maciej Nowak
The redboot-fis parser has option to specify the location of FIS
directory, use that, instead of patching the parser to scan for it, and
specifying location in kernel config.
Tested-by: Brian Gonyer
Signed-off-by: Tomasz Maciej Nowak
---
.../ath79/dts
From: Tomasz Maciej Nowak
This image is supposed to be written with help of bootloader to the
flash, but as it stands, it's not aligned to block size and RedBoot will
happily create non-aligned partition size in FIS directory. This could
lead to kernel to mark the partition as read
From: Tomasz Maciej Nowak
No reason to keep that around, since upstream one does the same.
Signed-off-by: Tomasz Maciej Nowak
---
.../ath79/dts/ar7161_adtran_bsap1880.dtsi | 2 +-
.../dts/bcm6348-inventel-livebox-1.dts| 2 +-
target/linux/gemini/image/Makefile| 4
From: Tomasz Maciej Nowak
Don't comence the switch to RAMFS when the image format is wrong. This
led to rebooting the device, which could lead to false impression that
upgrade succeded.
Being here, factor out the code responsible for upgrading RedBoot
devices to separate file.
Signed-o
From: Tomasz Maciej Nowak
This SBC has Microchip TCN75 sensor, wich measures ambient temperature.
Specify it in dts to allow readout by applications using kernel hwmon
API.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/ath79/dts/ar7161_jjplus_ja76pf2.dts | 13 +
target/linux
From: Tomasz Maciej Nowak
These narrowments are no longer useful, since there's no lower version
than 5.10 supported in tree.
Signed-off-by: Tomasz Maciej Nowak
---
package/kernel/linux/modules/crypto.mk | 2 +-
package/kernel/linux/modules/fs.mk | 10 --
package/k
From: Tomasz Maciej Nowak
This is now built-in, enable so it won't propagate on target configs.
Fixes: 79e7a2552e89 ("kernel: bump 5.15 to 5.15.44")
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/generic/config-5.15| 1 +
target/linux/rockchip/armv8/config-5.15
From: Tomasz Maciej Nowak
The MAC can be stored in OTP memory or in flash memory, currently the
driver could read it only from OTP. Backport the patch allowing setting
the MAC address from flash. Some modules have the OTP programmed but
the ODM/OEM decided to overwrite it with value stored in
From: Tomasz Maciej Nowak
The bootloader on this board hid the partition containig MAC addresses
and prevented adding this space to FIS directory, therefore those had to
be stored in RedBoot configuration as aliases to be able to assigne them
to proper interfaces. Now that fixed partition size
From: Tomasz Maciej Nowak
This image is supposed to be written with help of bootloader to the
flash, but as it stands, it's not aligned to block size and RedBoot will
happily create non-aligned partition size in FIS directory. This could
lead to kernel to mark the partition as read
From: Tomasz Maciej Nowak
Don't comence the switch to RAMFS when the image format is wrong. This
led to rebooting the device, which could lead to false impression that
upgrade succeded.
Being here, factor out the code responsible for upgrading RedBoot
devices to separate file.
Signed-o
From: Tomasz Maciej Nowak
After the kernel has switched version to 5.10, JA76PF2 and
RouterStations lost the capability to sysupgrade the OpenWrt version.
The cause is the lack of porting the patches responsible for partial
flash erase block writing and these boards FIS directory and RedBoot
W dniu 5.07.2022 o 12:21, Thibaut VARÈNE pisze:
> Hi,
Hi.
> Have you considered if CONFIG_MTD_SPI_NOR_USE_VARIABLE_ERASE[1] could maybe
> help there?
> It seems to address a similar issue (write-access to a 4K partition with 64K
> EB size).
That's a no-go, as in this particular case we would n
From: Tomasz Maciej Nowak
Forward-port from ar71xx target the board introduced in commit
eb9e3651dd1a (" ar71xx: add support for the MikroTik RB911-2Hn/5Hn
boards"). Follow intallation instruction from that commit message, using
images found in ath79 directory. Be advised that the boa
From: Tomasz Maciej Nowak
Most of boards from MikroTik with AR9344 SoC (supported and
un-supported) replicate the same schematic, so stack common device nodes
to a single dtsi.
Signed-off-by: Tomasz Maciej Nowak
---
v1 -> v2
- rebase
.../ar9344_mikrotik_routerboard-16m-nor.dtsi |
From: Tomasz Maciej Nowak
All boards which include this dtsi have a power LED, which is by default
ON on running system, so there's no need to replicate it. Let the user
decide what to do with it on running system.
Signed-off-by: Tomasz Maciej Nowak
---
v1 -> v2
- rebase
target/lin
W dniu 22.07.2022 o 11:31, Thibaut VARÈNE pisze:
> From: Thibaut VARENE
>
> Please don't do this.
> The rationale has been already explained here:
> https://github.com/openwrt/openwrt/pull/10135#pullrequestreview-1020528516
>
> The gist of it is: the power LED alone cannot disambiguate a powered
W dniu 6.08.2022 o 20:33, Hauke Mehrtens pisze:
> On 7/20/22 22:31, Tomasz Maciej Nowak wrote:
>> From: Tomasz Maciej Nowak
>>
>> Most of boards from MikroTik with AR9344 SoC (supported and
>> un-supported) replicate the same schematic, so stack common devic
W dniu 6.08.2022 o 20:33, Hauke Mehrtens pisze:
> On 7/20/22 22:31, Tomasz Maciej Nowak wrote:
>> From: Tomasz Maciej Nowak
>>
>> Forward-port from ar71xx target the board introduced in commit
>> eb9e3651dd1a (" ar71xx: add support for the MikroTik RB911-2Hn/5Hn
From: Tomasz Maciej Nowak
Most of boards from MikroTik with AR9344 SoC (supported and
un-supported) replicate the same schematic, so stack common device nodes
to a single dtsi.
ar9344_mikrotik_routerboard-16m-nor.dtsi:
- remove include paragraph and wmac node, make it single nor flash node
From: Tomasz Maciej Nowak
Forward-port from ar71xx target the board introduced in commit
eb9e3651dd1a (" ar71xx: add support for the MikroTik RB911-2Hn/5Hn
boards"). Citing:
The patch adds support for the MikroTik RB911-2Hn (911 Lite2)
and the RB911-5Hn (911 Lite5) boards
From: Tomasz Maciej Nowak
Adjusting dts will cause a rebuild of whole kernel as the buildroot
considers this a part of kernel source. It's a royal PITA when trying to
prepare support for new device, since this takes a lot of time on slower
systems. As it stands, buildroot itself, with own
From: Tomasz Maciej Nowak
Pakedge WR-1 is a dual-band wireless router.
Specification
SoC: Qualcomm Atheros IPQ4018
RAM: 256 MB DDR3
Flash: 32 MB SPI NOR
WIFI: 2.4 GHz 2T2R integrated
5 GHz 2T2R integrated
Ethernet: 5x 10/100/1000 Mbps QCA8075
USB: 1x 2.0
LEDS: 8x (3 GPIO controlled, 5
From: Tomasz Maciej Nowak
Calibration variants:
Pakedge-WR-1ETSI, FCC and IC-2.4GHz
Pakedge-WR-1-ACMA ACMA
Pakedge-WR-1-IC IC-5GHz
Pakedge-WR-1-SRRC SRRC
Signed-off-by: Tomasz Maciej Nowak
---
package/firmware/ipq-wifi/Makefile | 2 ++
.../ipq
W dniu 25.08.2022 o 13:32, Robert Marko pisze:
> On Wed, 24 Aug 2022 at 19:30, Tomasz Maciej Nowak wrote:
>>
>> From: Tomasz Maciej Nowak
>>
>> Adjusting dts will cause a rebuild of whole kernel as the buildroot
>> considers this a part of kernel source.
From: Tomasz Maciej Nowak
Adjusting dts will cause a rebuild of whole kernel as the buildroot
considers this a part of kernel source. It's a royal PITA when trying to
prepare support for new device, since this takes a lot of time on slower
systems. As it stands, buildroot itself, with own
From: Tomasz Maciej Nowak
Devices using GPT usually have FAT filesystem on boot partition and
that's where the intermediary backup of system configuration is stored
on sysupgrade. Automatic restoring of OpenWrt configuration after
sysupgrade will be inhibited if the driver is not loaded and
From: Tomasz Maciej Nowak
Creating overlay will fail if there's no loop device.
Signed-off-by: Tomasz Maciej Nowak
---
package/kernel/linux/modules/block.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/kernel/linux/modules/block.mk
b/package/kernel/
From: Tomasz Maciej Nowak
All contents of staging_dir/image are included in Image Builder (IB) in
case some binary needs to be included in final image. But in case of
this package, all sources are stored there and those clutter the final
tarball of IB for no reason. Those sources are not used
From: Tomasz Maciej Nowak
All contents of staging_dir/image are included in Image Builder (IB) in
case some binary needs to be included in final image. But in case of
this package, all sources are stored there and those clutter the final
tarball of IB for no reason. Those sources are not used
From: Tomasz Maciej Nowak
Simple copy to better illustrate the changes in forthcoming changes.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/tegra/config-5.15| 484 ++
...interrupts-due-to-tegra2-silicon-bug.patch | 77 +++
...enable-front-panel-leds-in
From: Tomasz Maciej Nowak
Calibration variants:
Pakedge-WR-1ETSI, FCC and IC-2.4GHz
Pakedge-WR-1-ACMA ACMA
Pakedge-WR-1-IC IC-5GHz
Pakedge-WR-1-SRRC SRRC
Signed-off-by: Tomasz Maciej Nowak
---
v1 -> v2
- no changes
package/firmware/ipq-wifi/Makef
From: Tomasz Maciej Nowak
- refresh config
- disable suspend as it's pointless in scope of OpenWrt
- enable CPU frequency scaling
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/tegra/Makefile| 1 +
target/linux/tegra/config-5.15 | 61 ++
2
From: Tomasz Maciej Nowak
Pakedge WR-1 is a dual-band wireless router.
Specification
SoC: Qualcomm Atheros IPQ4018
RAM: 256 MB DDR3
Flash: 32 MB SPI NOR
WIFI: 2.4 GHz 2T2R integrated
5 GHz 2T2R integrated
Ethernet: 5x 10/100/1000 Mbps QCA8075
USB: 1x 2.0
LEDS: 8x (3 GPIO controlled, 5
W dniu 6.09.2022 o 15:29, Tomasz Maciej Nowak pisze:
> From: Tomasz Maciej Nowak
>
> Simple copy to better illustrate the changes in forthcoming changes.
s/changes in//
Hope this gets squashed with second commit so I won't need to send v2.
>
> Signed-off-by:
W dniu 7.09.2022 o 00:15, Hauke Mehrtens pisze:
> On 8/31/22 17:03, Tomasz Maciej Nowak wrote:
>> From: Tomasz Maciej Nowak
>>
>> All contents of staging_dir/image are included in Image Builder (IB) in
>> case some binary needs to be included in final image. But in c
W dniu 7.09.2022 o 22:57, Hauke Mehrtens pisze:
> On 9/7/22 19:23, Tomasz Maciej Nowak wrote:
>> W dniu 7.09.2022 o 00:15, Hauke Mehrtens pisze:
>>> On 8/31/22 17:03, Tomasz Maciej Nowak wrote:
>>>> From: Tomasz Maciej Nowak
>>>>
>>>> A
From: Tomasz Maciej Nowak
All contents of staging_dir/image are included in Image Builder (IB) in
case some binary needs to be included in final image. But in case of
this package, all sources are stored there and those clutter the final
tarball of IB for no reason. Those sources are not used
From: Tomasz Maciej Nowak
- refresh config
- disable suspend as it's pointless in the sope of OpenWrt
- enable CPU frequency scaling
Signed-off-by: Tomasz Maciej Nowak
---
v1 -> v2
- fix unresolved symbols pointed by Petr
target/linux/tegra/Makefile| 1 +
target/linux/tegra/con
From: Tomasz Maciej Nowak
Simple copy to better illustrate the forthcoming changes.
Signed-off-by: Tomasz Maciej Nowak
---
v1 -> v2
- fix commit message
target/linux/tegra/config-5.15| 484 ++
...interrupts-due-to-tegra2-silicon-bug.patch | 77 +++
...ena
From: Tomasz Maciej Nowak
On OEM firmware both addresses for In and Out ports are different. Set
them as such also in OpenWrt.
Fixes: e24635710c7e (" ipq40xx: add support for Luma Home WRTQ-329ACN")
Signed-off-by: Tomasz Maciej Nowak
---
.../arch/arm/boot/dts/qcom-ipq4018-wrtq-
From: Tomasz Maciej Nowak
Fix this occurence during boot:
/bin/board_detect: line 10: Unsupported: not found
Fixes: 80baffd2aa91 (" ipq40xx: add support for Pakedge WR-1")
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/ipq40xx/base-files/etc/board.d/02_network | 1 +
1 file
From: Tomasz Maciej Nowak
And enable the device.
Signed-off-by: Tomasz Maciej Nowak
---
.../ipq40xx/base-files/etc/board.d/02_network | 1 +
.../arch/arm/boot/dts/qcom-ipq4018-wr-1.dts | 37 +++
target/linux/ipq40xx/image/generic.mk | 3 +-
3 files changed, 39
From: Tomasz Maciej Nowak
And enable the device.
Signed-off-by: Tomasz Maciej Nowak
---
.../ipq40xx/base-files/etc/board.d/02_network | 1 +
.../arm/boot/dts/qcom-ipq4018-wrtq-329acn.dts | 55 +--
target/linux/ipq40xx/image/generic.mk | 3 +-
3 files changed, 41
From: Tomasz Maciej Nowak
Adjust them according to OEM firmware.
Fixes: e24635710c7e (" ipq40xx: add support for Luma Home WRTQ-329ACN")
Signed-off-by: Tomasz Maciej Nowak
---
This is different than
https://patchwork.ozlabs.org/project/openwrt/patch/20220923124739.5979-1,
wher
From: Tomasz Maciej Nowak
Adjust them according to OEM firmware.
Fixes: e24635710c7e (" ipq40xx: add support for Luma Home WRTQ-329ACN")
Signed-off-by: Tomasz Maciej Nowak
---
.../files/arch/arm/boot/dts/qcom-ipq4018-wrtq-329acn.dts | 5 +
1 file changed, 5 insertions(+)
W dniu 20.10.2022 o 23:04, Tim Harvey pisze:
> Greetings,
>
> How would I go about getting a file added to the list of Image Files
> or Supplementary Files made by the auto-builder?
>
> For the octeontx target the kernel should be provided as a downloadable as
> well.
I'm not exactly sure, but
already exists for some
time. Unfortunately I didn't test it, as the board I wanted to use it has gone
in flames. For ready to use recipe see the attachment. Feel free to submit it
to packages feed and take over maintainership after giving it a test.
> [1] http://lists.openwrt.org/
From: Tomasz Maciej Nowak
It seems more hardware needs early load of firmware when initialised
to work properly (at least Intel hardware). One of previous case is CPU
microcode, which this series[1] tried to change. The second one is Intel
graphics IC, which needs firmware for controlling DMC
From: Tomasz Maciej Nowak
This hack was to bring all existing installations to the newest GRUB
version as fast as possible. Since 19.07.x is EoL we can assume this
task is completed. Now sysupgrade will solely be responsible for
bootloader upgrade.
Signed-off-by: Tomasz Maciej Nowak
---
Some
From: Tomasz Maciej Nowak
This hack was to bring all existing installations to the newest GRUB
version as fast as possible. Since 19.07.x is EoL we can assume this
task is completed. Now sysupgrade will solely be responsible for
bootloader upgrade.
Signed-off-by: Tomasz Maciej Nowak
From: Tomasz Maciej Nowak
Match interface numbers with printed numbers on device enclosure and
assign first port as WAN interface.
Notes
Serial console is available through RJ-45 port with Cisco pinout
baud: 19200, parity: none, flow control: none
The device is setup with UEFI. To enter setup
From: Tomasz Maciej Nowak
Some packages offer functionalities guarded by these options and it'll
be impossible to reach them without changing Config-build.in. So allow
to toggle these in more friendly way, by exposing them in configuration
menu.
Signed-off-by: Tomasz Maciej Nowak
---
t
Align subtargets makefiles names to actual subtargets.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/Makefile| 6 +++---
target/linux/mvebu/image/{cortex-a53.mk => cortexa53.mk} | 0
target/linux/mvebu/image/{cortex-a72.mk => cortexa72.mk} | 0
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/cortex-a72.mk | 30 ++--
target/linux/mvebu/image/cortex-a9.mk | 198 -
2 files changed, 114 insertions(+), 114 deletions(-)
diff --git a/target/linux/mvebu/image/cortex-a72.mk
b/target/linux/mvebu/image
These variables are already initialized within DEVICE_VARS. Just move
DEVICE_VARS to make sure they are set before default profile.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/Makefile | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/target/linux/mvebu
Most of changes are purely cosmetic, with bigger chages to uDPU. This
will be the last of this type of clen-up from me.
Tomasz Maciej Nowak (8):
mvebu: image: sort devices alphabetically
mvebu: image: align subtargets makefile names
mvebu: image: drop empty variables from default profile
Don't rewrite global DTS_DIR, instead, use proper variable for
specifying devices dts directory.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/mvebu/image/Makefile
b/target/linux/
This device receipe selects bunch of packages, which some are re-defined,
unnecessary or irrelevant. Clean them up, so only basic functionality
persist.
Cc: Scott Roberts
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/cortexa53.mk | 4 +---
1 file changed, 1 insertion(+), 3
Tar has ability to change current dir, so use that instead additional
command invocation. Also being here, change tar arguments to make final
archive reproducible.
Cc: Scott Roberts
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/Makefile | 12 +---
1 file changed, 9
If device recipe has specified DEVICE_DTS variable, the dtb is built
anyway by OpenWrt buildroot image rules. Drop the patch and adjust the
location of compiled dtb.
Cc: Scott Roberts
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/cortexa53.mk | 2
The BUILD_VARIANT might differ from UBOOT_CONFIG, so point to a file we
are actually changing. Being here let's call 'Build/Configure/U-Boot'
definition, instead of definig the same command. This'll be more future
proof, if U-Boot configuration procedure will change.
Signed-o
o dtb. The only thing that
differs is the location where it'll end up.
Regards
>
> Scott
>
> On Fri, Jan 31, 2020 at 8:47 AM Tomasz Maciej Nowak wrote:
>
>> If device recipe has specified DEVICE_DTS variable, the dtb is built
>> anyway by OpenWrt buildroot imag
Hi Adrian.
W dniu 31.01.2020 o 16:56, Adrian Schmutzler pisze:
> Hi,
>
>> -Original Message-
>> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
>> Behalf Of Tomasz Maciej Nowak
>> Sent: Freitag, 31. Januar 2020 16:46
>>
W dniu 31.01.2020 o 17:02, Adrian Schmutzler pisze:
> Hi,
>
>> -Original Message-
>> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
>> Behalf Of Tomasz Maciej Nowak
>> Sent: Freitag, 31. Januar 2020 16:46
>> To: openwrt-devel@li
Adrian
>
Regards
>>
>>> So, setting the variables to "" in the default definition actually makes
>>> sure
>>> that they really are zero for those devices where they are not set. (Of
>>> course,
>>> typically those are the devi
W dniu 31.01.2020 o 19:47, Adrian Schmutzler pisze:
> Hi,
>
>> -Original Message-----
>> From: Tomasz Maciej Nowak [mailto:tome...@o2.pl]
>> Sent: Freitag, 31. Januar 2020 19:39
>> To: Adrian Schmutzler ; openwrt-
>> de...@lists.openwrt.org
>> Subj
The BUILD_VARIANT might differ from UBOOT_CONFIG, so point to a file we
are actually changing. Being here let's call 'Build/Configure/U-Boot'
definition, instead of definig the same command. This'll be more future
proof, if U-Boot configuration procedure will change.
Signed-o
empty variables from default profile
- add DEVICE_DTS_DIR variable to global profile, as suggested by Adrian
Schmutzler
mvebu: image: keep global DTS_DIR intact
Tomasz Maciej Nowak (5):
mvebu: image: keep global DTS_DIR intact
mvebu: uDPU: clean package selection
mvebu: image: rework uDPU
This device receipe selects bunch of packages which some are re-defined,
unnecessary or irrelevant. Clean them up, so only basic functionality
persist.
Cc: Scott Roberts
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/cortexa53.mk | 4 +---
1 file changed, 1 insertion(+), 3
If device recipe has specified DEVICE_DTS variable, the dtb is built
anyway by OpenWrt buildroot image rules. Drop the patch and adjust the
location of compiled dtb.
Cc: Scott Roberts
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/cortexa53.mk | 2
Don't rewrite global DTS_DIR, instead, use proper variable for
specifying devices dts directory. For consistency, also specify the
variable in default profile, as suggested by Adrian Schmutzler.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/Makefile | 3 ++-
1 file chang
Tar has ability to change current dir, so use that instead additional
command invocation. Also being here, change tar arguments to make final
archive reproducible.
Cc: Scott Roberts
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/Makefile | 12 +---
1 file changed, 9
301 - 400 of 583 matches
Mail list logo
