On 29/03/2022 16:29, Rafał Miłecki wrote:
On 12.11.2021 11:56, Arınç ÜNAL wrote:
Asus RT-AC88U is an AC3100 router featuring 9 Ethernet ports over the
integrated Broadcom and the external Realtek switch.
Hardware info:
* Processor: Broadcom BCM4709C0KFEBG dual-core @ 1.4 GHz
* Switch: BCM53012
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 ---
Hi Team,
I want to build a
On 12.11.2021 11:56, Arınç ÜNAL wrote:
Asus RT-AC88U is an AC3100 router featuring 9 Ethernet ports over the
integrated Broadcom and the external Realtek switch.
Hardware info:
* Processor: Broadcom BCM4709C0KFEBG dual-core @ 1.4 GHz
* Switch: BCM53012 in BCM4709C0KFEBG & external RTL8365MB
*
> On 29. Mar 2022, at 12:45, Hauke Mehrtens wrote:
>
> On 3/25/22 17:35, Paul Spooren wrote:
>> Looks good to me. I’m just wondering if LuCI will pull in dnsmasq et al
>> again for release builds.
>
> Stijn tested this on top of OpenWrt 22.03 branch successfully. He also
> activated LuCI
I extended the reasoning in the commit message and merged this as discussed in
IRC
> On 28. Feb 2022, at 11:49, Paul Spooren wrote:
>
>
>
>> On 28. Feb 2022, at 12:35, Stijn Tintel wrote:
>>
>> On 28/02/2022 13:22, Paul Spooren wrote:
>>> Hi team,
>>>
On 19. Feb 2022, at 19:21,
On 3/25/22 17:35, Paul Spooren wrote:
Looks good to me. I’m just wondering if LuCI will pull in dnsmasq et al again
for release builds.
Stijn tested this on top of OpenWrt 22.03 branch successfully. He also
activated LuCI and dnsmasq was not pulled in.
Hauke
Piotr Dymacz [2022-03-29 10:10:00]:
Hi,
> It seems I've been misusing 'target' for a long time and now I'm trying to
> understand how this leads to the same behavior as 'platform' :)
comments right above that code states following:
# defaults to subtarget if subtarget exists and target does
Hi Petr,
On 29.03.2022 08:34, Petr Štetiar wrote:
Make it clear, that for `make kernel_{menu,old}config` it's possible to
use only following values for CONFIG_TARGET variable:
* env
* platform
* subtarget
* subtarget_platform
It seems I've been misusing 'target' for a long time and
Make it clear, that for `make kernel_{menu,old}config` it's possible to
use only following values for CONFIG_TARGET variable:
* env
* platform
* subtarget
* subtarget_platform
This should prevent misuse like `make kernel_menuconfig CONFIG_TARGET=bcm2710`
etc.
Signed-off-by: Petr Štetiar
