From: Tomasz Maciej Nowak
Dell/SonicWall APL26-0AE (marketed as SonicPoint ACe) is a dual band
wireless access point. End of life as of 2022-07-31.
Specification
SoC: QualcommAtheros QCA9550
RAM: 256 MB DDR2
Flash: 32 MB SPI NOR
WIFI: 2.4 GHz 3T3R integrated
5 GHz 3T3R QCA9890 oversized
From: Tomasz Maciej Nowak
Dell/SonicWall APL26-0AE (marketed as SonicPoint ACe) is a dual band
wireless access point. End of life as of 2022-07-31.
Specification
SoC: QualcommAtheros QCA9550
RAM: 256 MB DDR2
Flash: 32 MB SPI NOR
WIFI: 2.4 GHz 3T3R integrated
5 GHz 3T3R QCA9890 oversized
W dniu 15.04.2024 o 14:32, Paul D pisze:
>
>>> 6. Adjust "ipaddr" (access point) and "serverip" (TFTP server) addresses
> Might be an idea to explicitly document these IPs so that dedicated users can
> already set their gear to those IPs and just smash enter
Will add them in v2, but given the
W dniu 13.04.2024 o 16:05, Tomasz Maciej Nowak pisze:
> From: Tomasz Maciej Nowak
>
> Dell/SonicWall APL26-0AE (marketed as SonicPoint ACe) is a dual band
> wireless access point.
>
> Specification
> SoC: QualcommAtheros QCA9550
> RAM: 256 MB DDR2
> Flash: 32 MB S
From: Tomasz Maciej Nowak
Dell/SonicWall APL26-0AE (marketed as SonicPoint ACe) is a dual band
wireless access point.
Specification
SoC: QualcommAtheros QCA9550
RAM: 256 MB DDR2
Flash: 32 MB SPI NOR
WIFI: 2.4 GHz 3T3R integrated
5 GHz 3T3R QCA9890 oversized Mini PCIe card
Ethernet: 2x 10
W dniu 29.03.2024 o 19:08, Elliott Mitchell pisze:
> On Fri, Mar 29, 2024 at 04:32:18PM +0100, Paul D wrote:
>> Recommend avoiding -a and -o params.
>>
>> Use instead e.g.
>>
>> [ -n "$GUID" ] || [ "$KERNELPARTTYPE" = "6" ] || [ "$KERNELPARTTYPE" = "c" ]
>>
>>
From: Tomasz Maciej Nowak
Some old or proprietary bootloader recognise only FAT file system
variants on storage devices with MBR but unfortunately script ties
format of kernel partition to GPT partition table. So, allow kernel
partition file system to be FAT16 or FAT32 if appropriate type is set
W dniu 29.03.2024 o 09:57, Robert Marko pisze:
> On Thu, 28 Mar 2024 at 18:03, Tomasz Maciej Nowak wrote:
>>
>> From: Tomasz Maciej Nowak
>>
>> Introduced WoL feature needs CRC16 support.
>>
>> Signed-off-by: Tomasz Maciej Nowak
>> ---
>> pack
From: Tomasz Maciej Nowak
Introduced WoL feature needs CRC16 support.
Signed-off-by: Tomasz Maciej Nowak
---
v1 -> v2
- strictly depend on 6.6 version
package/kernel/linux/modules/netdevices.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/kernel/linux/modu
From: Tomasz Maciej Nowak
Introduced WoL feature needs CRC16 support.
Signed-off-by: Tomasz Maciej Nowak
---
package/kernel/linux/modules/netdevices.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/kernel/linux/modules/netdevices.mk
b/package/kernel/linux
From: Tomasz Maciej Nowak
Some old or proprietary bootloader recognize only FAT file system
variants on storage devices with MBR, unfortunately script ties
format of kernel partition to GPT partition table. So, allow kernel
partition file system to be FAT16 or FAT32 if appropriate type is set
From: Tomasz Maciej Nowak
This guard is unnecessary, since target using these recipes are already
exempted from running in Image Builder.
Signed-off-by: Tomasz Maciej Nowak
---
include/image.mk | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/image.mk b/include/image.mk
index
From: Tomasz Maciej Nowak
Device tree blobs are arch agnostic, so we don't need to cross compile
them.
Signed-off-by: Tomasz Maciej Nowak
---
include/image.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/image.mk b/include/image.mk
index 4b6acbe1aad6
From: Tomasz Maciej Nowak
Image Builder includes target dts which might reference device tree
bindings for various integrated peripherals and trying to build dtb
without access to bindings will fail.
Signed-off-by: Tomasz Maciej Nowak
---
target/imagebuilder/Makefile | 5 -
1 file changed
From: Tomasz Maciej Nowak
Because some still unresolved bugs in this driver, which sprout
occasional questions what this patch works around, point to the issue
which started this. Being here, fill headers required by git am.
Signed-off-by: Tomasz Maciej Nowak
---
v1 -> v2
- rebase
.../mv
From: Tomasz Maciej Nowak
Fails with following errors on MacOS builder:
[ 96%] Building C object CMakeFiles/zycast.dir/src/zycast.c.o
/usr/bin/gcc
-I/Users/runner/work/firmware-utils/firmware-utils/openwrt/tools/include
-I/usr/local/opt/libressl/include -O3 -DNDEBUG -isysroot
/Applications
From: Tomasz Maciej Nowak
Because some still unresolved bugs in this driver, which sprout
occasional questions what this patch works around, point to the issue
which started this. Being here, fill headers required by git am.
Signed-off-by: Tomasz Maciej Nowak
---
.../mvebu/patches-5.15/700
From: Tomasz Maciej Nowak
TP-Link RE365 is a wireless range extender, hardware-wise resembles
RE305 with slight changes regarding buttons and LEDs.
Specification
SoC: MediaTek MT7628AN
RAM: 64 MiB DDR2
Flash: 8 MiB SPI NOR
WiFi: 2.4 GHz 2T2R integrated
5 GHz 2T2R MediaTek MT7612EN
From: Tomasz Maciej Nowak
Some of devices in this target have only 8 MiB space and are closing to
borders of usable space. Particularly, TP-Link RE305 v1 already suffers
from this issue[1], where with current partition layout, on release
images, there's not enough space for overlay. So activate
W dniu 7.01.2024 o 14:06, Sander Vanheule pisze:
> Hi Tomasz,
>
> On Fri, 2023-12-22 at 11:36 +0100, Tomasz Maciej Nowak wrote:
>> From: Tomasz Maciej Nowak
>>
>> TP-Link RE365 is a wireless range extender, hardware-wise resembles
>> RE305 with slight c
From: Tomasz Maciej Nowak
TP-Link RE365 is a wireless range extender, hardware-wise resembles
RE305 with slight changes regarding buttons and LEDs.
Specification
SoC: MediaTek MT7628AN
RAM: 64 MiB DDR2
Flash: 8 MiB SPI NOR
WiFi: 2.4 GHz 2T2R integrated
5 GHz 2T2R MediaTek MT7612EN
From: Tomasz Maciej Nowak
Partition layout same as RE305 v1. Values extracted from vendor
firmware. This will only be used for creating factory image.
Signed-off-by: Tomasz Maciej Nowak
---
src/tplink-safeloader.c | 38 ++
1 file changed, 38 insertions
From: Tomasz Maciej Nowak
TP-Link RE365 is a wireless range extender, hardware-wise similar to
RE305 with slight changes regarding buttons and LEDs.
Specification
SoC: MediaTek MT7628AN
RAM: 64 MiB DDR2
Flash: 8 MiB SPI NOR
WiFi: 2.4 GHz 2T2R integrated
5 GHz 2T2R MediaTek MT7612EN
al media on USB. I have used
> it successfully as a NAS with ksmbd and LUCI web API, see:
> https://dflund.se/~triad/krad/ixp4xx/
>
> Signed-off-by: Howard Harte
> Signed-off-by: Linus Walleij
Thank You for following suggestions, with that:
Reviewed-by: Tomasz Maciej Nowak
W dniu 4.10.2023 o 19:11, Jonas Gorski pisze:
> Hi,
>
> On Thu, 28 Sept 2023 at 15:29, Linus Walleij wrote:
>>
>> XP4xx was deleted because of lack of maintenance in 2020.
>>
>> In the years since, the upstream Linux support for IXP4xx has
>> been rewritten from scratch. It is now pretty well
Hi,
some comments inline.
W dniu 28.09.2023 o 15:28, Linus Walleij pisze:
> This resurrects the support for IXP4xx using device tree
> rather than the old (deleted) board files. The final pieces
> of IXP4xx board files were deleted in Linux v5.19.
>
> Ext4 root filesystems on CF and USB are
From: Tomasz Maciej Nowak
Since kernel 5.13 this is needed to enable USB ports on all devices in
subtarget. Previously TF-A and COMPHY driver might have set up this PHY,
but not anymore.
Signed-off-by: Tomasz Maciej Nowak
Tested-by: Robert Marko
(cherry picked from commit
From: Tomasz Maciej Nowak
Since kernel 5.13 this is needed to enable USB ports on all devices in
subtarget. Previously TF-A and COMPHY driver might have set up this PHY,
but not anymore.
Signed-off-by: Tomasz Maciej Nowak
---
Please backport config-5.15 changes to 23.05 and 22.03 branches
From: Tomasz Maciej Nowak
This should be a part of kernel major bump. Fortunately it didn't stall
compilation, so no fixes tag.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/config-6.1 | 26 ++---
target/linux/mvebu/cortexa53/config-6.1 | 10
From: Tomasz Maciej Nowak
Backport didn't include changes to mkubntimage invocation, which allowed
to pass arguments. This in result produces broken routerstation factory
images, which have kernel embedded as kernel partition instead of LZMA
loader.
Fixes: #13260
Fixes: 8e09f9ffc3cc ("
From: Tomasz Maciej Nowak
- refresh patches
- adjust kernel config, with main change enabling VIDEO_TEGRA_VDE,
necessary for driving power domain responsible for clean reboot
- adjust LED patch to changes in LED drivers
Signed-off-by: Tomasz Maciej Nowak
---
package/kernel/linux/modules
From: Tomasz Maciej Nowak
Testing results were all good, so move target to newer kernel by default.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/tegra/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/tegra/Makefile b/target/linux/tegra/Makefile
From: Tomasz Maciej Nowak
Prepare for addition of kernel 6.1 support.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/tegra/config-6.1 | 504 ++
...interrupts-due-to-tegra2-silicon-bug.patch | 77 +++
...enable-front-panel-leds-in-TrimSlice.patch | 46
From: Tomasz Maciej Nowak
Straightforward update and small generic config modification.
Tomasz Maciej Nowak (4):
kernel: 6.1: move NO_ARRAY_BOUNDS to generic
tegra: copy patches and config for kernel 6.1
tegra: initial kernel 6.1 support
tegra: switch to 6.1 kernel
package/kernel
From: Tomasz Maciej Nowak
Array bounds are disabled for GCC 11 or later. It's better to track it in
global (generic) config.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/bcm27xx/bcm2708/config-6.1 | 2 --
target/linux/bcm27xx/bcm2709/config-6.1 | 2 --
target/linux/bcm27xx/bcm2710
From: Tomasz Maciej Nowak
Alter booting command in U-Boot on first boot after upgrade to workaround
the kernel size limitation. The kernel size read from flash will be 8MiB,
which should suffice for forseable future. As precaution a warning
interupting upgrade is emited, explaining what to do
From: Tomasz Maciej Nowak
'bootipq' command on some devices, with kernel on NOR flash chip, read
kernel partition size from Qualcomm proprietary partition table, which
seems to be stored in MIBIB partition. The partition table can be read
by 'smeminfo' command in U-Boot command line interface
From: Tomasz Maciej Nowak
Some of devices having kernel on NOR flash could reach limit of kernel
partition size at 4MiB and soft-brick them. Unfortunately we don't know
if all of them are affected, thus kernel size limit is added to all of
remaining ones. Later commit allows for some devices
From: Tomasz Maciej Nowak
Devices allowing to boot LZMA or GZIP compressed kernel didn't hit yet
the 4MiB boundary for kernel size, thus allowing to prepare workaround
for the issue, without need for serial console attachment.
The workaround is modifying 'bootcmd' variable in U-Boot environment
W dniu 25.07.2023 o 12:27, Robert Marko pisze:
> On Mon, 24 Jul 2023 at 15:31, Tomasz Maciej Nowak wrote:
>>
>> From: Tomasz Maciej Nowak
>>
>> 'bootipq' command on some devices, with kernel on NOR flash chip, read
>> kernel partition size from Qualcomm p
From: Tomasz Maciej Nowak
Some of devices having kernel on NOR flash could reach limit of kernel
partition size at 4MiB and soft-brick them. Unfortunately we don't know
if all of them are affected, thus kernel size limit is added to all of
remaining ones. Later commit allows for some devices
From: Tomasz Maciej Nowak
Alter booting command in U-Boot on first boot after upgrade to workaround
the kernel size limitation. The kernel size read from flash will be 8MiB,
which should suffice for forseable future. As precaution a warning
interupting upgrade is emited, explaining what to do
From: Tomasz Maciej Nowak
'bootipq' command on some devices, with kernel on NOR flash chip, read
kernel partition size from Qualcomm proprietary partition table, which
seems to be stored in MIBIB partition. The partition table can be read
by 'smeminfo' command in U-Boot command line interface
From: Tomasz Maciej Nowak
Devices allowing to boot LZMA compressed kernel or zImage kernel didn't
hit yet the 4MiB boundary for kernel size, thus allowing to prepare
workaround for the issue, without need for serial console attachment.
The workaround is modifying 'bootcmd' variable in U-Boot
W dniu 11.07.2023 o 16:09, Tomasz Maciej Nowak pisze:
> From: Tomasz Maciej Nowak
>
> 'help' target fails not finding a file, so follow up on a change[2] made
> as a fix for main README[1].
>
> 1. d0113711a31f ("README: port to 21st century")
> 2. 751486b31fd9 (
From: Tomasz Maciej Nowak
Some device recipes remove default target packages. If user tries to add
them back they will be ignored, since packages list is processed in one
go. Process the device recipe packages first and do user ones later, so
additions won't get filtered out.
Signed-off
From: Tomasz Maciej Nowak
'help' target fails not finding a file, so follow up on a change[2] made
as a fix for main README[1].
1. d0113711a31f ("README: port to 21st century")
2. 751486b31fd9 ("build: fix README.md reference after rename")
Signed-off-by: Tomasz Maciej No
W dniu 10.07.2023 o 00:16, Felix Baumann pisze:
> Am 9. Juli 2023 23:26:13 MESZ schrieb Tomasz Maciej Nowak :
>> W dniu 9.07.2023 o 12:43, Felix Baumann pisze:
>>> Am 7. Juli 2023 17:11:43 MESZ schrieb Tomasz Maciej Nowak
>>> :
>>>> From: Tomasz Maciej Nowak
W dniu 9.07.2023 o 12:43, Felix Baumann pisze:
> Am 7. Juli 2023 17:11:43 MESZ schrieb Tomasz Maciej Nowak :
>> From: Tomasz Maciej Nowak
>>
>> Alter command boot sequence in U-Boot on first boot after upgrade to
>> workaround the kernel size limitation. The
From: Tomasz Maciej Nowak
This has been a part of modified upstream patch but got lost on major
kernel bump to 5.15, so bring it back.
Signed-off-by: Tomasz Maciej Nowak
---
Please backport to 23.05 branch
...vell-enable-heartbeat-LED-by-default.patch | 22 +++
1 file
From: Tomasz Maciej Nowak
Devices allowing to boot LZMA compressed kernel or zImage kernel didn't
hit yet the 4MiB boundary for kernel size, thus allowing to prepare
workaround for the issue, without need for serial console attachment.
The workaround is modifying 'bootcmd' variable in U-Boot
From: Tomasz Maciej Nowak
Alter command boot sequence in U-Boot on first boot after upgrade to
workaround the kernel size limitation. The kernel size read from flash
will be 8MiB, which should suffice for forseable future. As precaution a
warning interupting upgrade is emited, explaining what
From: Tomasz Maciej Nowak
Some of devices having kernel on NOR flash could reach limit of kernel
partition size at 4MiB and soft-brick them. Unfortunately we don't know
if all of them are affected, thus kernel size limit is added to all of
remaining ones. Later commit allows for some devices
From: Tomasz Maciej Nowak
'bootipq' command, on some devices with kernel on NOR flash chip, read
kernel partition size from Qualcomm proprietary partition table, which
seems to be stored in MIBIB partition. The partition table can be read
by 'smeminfo' command in U-Boot command line interface
From: Tomasz Maciej Nowak
Devices allowing to boot LZMA compressed kernel or zImage kernel didn't
hit yet the 4MiB boundary for kernel size, thus allowing to prepare
workaround for the issue, without need for serial console attachment.
The workaround is modifying 'bootcmd' variable in U-Boot
From: Tomasz Maciej Nowak
Some of devices having kernel on NOR flash could reach limit of kernel
partition size at 4MiB and soft-brick them. Unfortunately we don't know
if all of them are affected, thus kernel size limit is added to all of
remaining ones. Later commit allows for some devices
From: Tomasz Maciej Nowak
Alter command boot sequence in U-Boot on first boot after upgrade to
workaround the kernel size limitation. The kernel size read from flash
will be 8MiB, which should suffice for forseable future. As precaution a
warning interupting upgrade is emited, explaining what
From: Tomasz Maciej Nowak
'bootipq' command, on some devices with kernel on NOR flash chip, read
kernel partition size from Qualcomm proprietary partition table, which
seems to be stored in MIBIB partition. The partition table can be read
by 'smeminfo' command in U-Boot command line interface
W dniu 1.06.2023 o 18:58, Philip Prindeville pisze:
> Hi,
Hi.
> I'm thinking about the utility of being able to build a generalized ARM64
> image (not "armvirt") for bring up on new platforms for testing.
>
> There are a lot of generalized computing platforms like the Ampere Altra
> servers
From: Tomasz Maciej Nowak
On each generation of the archive check sum will differ, because when
checking out subversion repository, current date is used for directories
creation. Force tar to assign creation date of the last revision for all
items inside archive.
Signed-off-by: Tomasz Maciej
From: Christian Marangi
Refresh swconfig_leds source to handle new trigger locking that is now a
spinlock.
Signed-off-by: Christian Marangi
---
.../files/drivers/net/phy/swconfig_leds.c| 16
1 file changed, 16 insertions(+)
diff --git
From: Tomasz Maciej Nowak
This helper has been renamed looong time ago, and with
ba530fea8ca1 ("ethernet: remove random_ether_addr()") the old name is no
longer available, so rename accordingly.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/generic/files/drivers/bcma/fallba
From: Tomasz Maciej Nowak
As of ed5c2f5fd10d ("i2c: Make remove callback return void") return
value of remove function is ignored.
Signed-off-by: Tomasz Maciej Nowak
---
package/kernel/ubnt-ledbar/src/leds-ubnt-ledbar.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/pack
From: Tomasz Maciej Nowak
Small set of non-invasive compat code preping support for 6.1 kernel
with two additional cosmetic commits. Should not break buildability of
touched parts.
Christian Marangi (2):
kernel: refresh IFF_NO_IP_ALIGN ifdef for kernel >= 6.1
kernel: refresh swconfig_l
From: Tomasz Maciej Nowak
These patches were accepted during 6.2 merge window, so rename
accordingly.
Signed-off-by: Tomasz Maciej Nowak
---
...-01-v6.2-net-ethernet-mtk_wed-introduce-wed-mcu-support.patch} | 0
...9-02-v6.2-net-ethernet-mtk_wed-introduce-wed-wo-support.patch} | 0
2-net
From: Tomasz Maciej Nowak
It's only used on devices in mt7621 and mt7622 subtargets, so no reason
to compile it for others.
Signed-off-by: Tomasz Maciej Nowak
---
package/kernel/ubnt-ledbar/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/kernel/ubnt-ledbar
From: Christian Marangi
Kernel 6.1 expanded the priv_flags to long bitmap so update and restore
it to priv_flags.
Signed-off-by: Christian Marangi
---
target/linux/ath25/files/drivers/net/phy/mvswitch.c | 8 ++--
target/linux/generic/files/drivers/net/phy/ar8216.c | 8 ++--
2 files
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
---
v1 ->
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
---
target
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
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
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
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
ome
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/pipermail/openwrt-devel/2
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
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(+)
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,
wh
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
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
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
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
- 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/config-5
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
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
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 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: Toma
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
- 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 files
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
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
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
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/linux
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 file
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 rule
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 sour
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
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 rule
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
1 - 100 of 522 matches
Mail list logo
