rules.mk always passes these as -I/-L to the toolchain.
Fixes rare errors like:
cc1: error: staging_dir/target-aarch64_cortex-a53_musl/usr/include: No such
file or directory [-Werror=missing-include-dirs]
Signed-off-by: Andre Heider
---
tools/Makefile | 2 +-
1 file changed, 1 insertion(+), 1
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 ---
Hey Scott,
Are you aware of our h
I see this is getting mixed with other patches, so to be clear this is
a patch for firewall3 (see
https://bugs.openwrt.org/index.php?do=details&task_id=3284).
Let me know if there is a better place to post this.
Le sam. 15 août 2020 à 13:50, a écrit :
>
> From: Remi NGUYEN VAN
>
> Boolean attri
Too much effort to say "No interest at this time?"
On Aug 19, 2020: 23:25, Piotr Dymacz wrote:
Hi Scott,
On 18.08.2020 23:27, Heppler, J. Scott wrote:
request.
Reply-To:
Organization:
I sent an email to cont...@openwrt.org, subject line Trademark Use
Request, inquiring about crowd funding an
Hi Scott,
On 18.08.2020 23:27, Heppler, J. Scott wrote:
request.
Reply-To:
Organization:
I sent an email to cont...@openwrt.org, subject line Trademark Use
Request, inquiring about crowd funding an OpenWrt router. I never
received a reply. The email gave the background, links to forum
discuss
From: Ataberk Özen
This commit adds support for Xiaomi's Mi Router 4C device.
Specifications:
- CPU: MediaTek MT7628AN (580MHz)
- Flash: 16MB
- RAM: 64MB DDR2
- 2.4 GHz: IEEE 802.11b/g/n with Integrated LNA and PA
- Antennas: 4x external single band antennas
- WAN: 1x 10/100M
- LAN: 2x 10/100M
Hi Adrian,
Nice catch :D.
I didn’t see this pair when I removed the applied and reverted patches.
P.D: I didn’t see the v2 >.<
Acked-by: Álvaro Fernández Rojas
> El 19 ago 2020, a las 13:49, Adrian Schmutzler
> escribió:
>
> Patch 1 introduces a change, and patch 2 reverts it again. Remove
Hi Adrian,
Nice catch :D.
I didn’t see this pair when I removed the applied and reverted patches.
Acked-by: Álvaro Fernández Rojas
> El 19 ago 2020, a las 13:33, Adrian Schmutzler
> escribió:
>
> Patch 1 introduces a change, and patch 2 reverts it again. Remove
> both patches and achieve the
The approach I was taking was based on choosing the actual chips based
on developer input and then find a HW who can provide based on those
recommendations.
I also lean toward a lower price point for an initial production run -
this is new ground and it lowers financial risk. The initial run, if
Patch 1 introduces a change, and patch 2 reverts it again. Remove
both patches and achieve the same outcome.
Refreshed patches for the target as well.
Cc: Álvaro Fernández Rojas
Signed-off-by: Adrian Schmutzler
---
...m-Fix-platform-device-unregistration.patch | 27 -
...m-Regi
To parse the ELF kernel loader, a small ELF parser is used that can
handle both ELF32 or ELF64 class loaders. The splitter assumes that the
kernel is always located before the rootfs, whether it is embedded in
the loader or not. If the kernel is located after the rootfs on the
firmware partition, t
Patch 1 introduces a change, and patch 2 reverts it again. Remove
both patches and achieve the same outcome.
Cc: Álvaro Fernández Rojas
Signed-off-by: Adrian Schmutzler
---
...m-Fix-platform-device-unregistration.patch | 27 -
...m-Unify-the-unload-handling-of-platf.patch | 29 -
You seem to ask for two things:
- firmware support
- permission to label the router an "official OpenWrt Router"
Wouldn't it be possible to develop the firmware on your own or to hire some
developer for that task? Or maybe ask for volunteers.
And for the branding you can probably highlight the Op
13 matches
Mail list logo
