On Tue, Jan 10, 2023 at 11:06:51PM -0800, Brian Norris wrote:
> To bring in isatty() support.
>
> Includes new commits:
>
> dad974baa46 Merge pull request #137 from ynezz/ynezz/isatty
> be30472bfdbb fs: add `isatty()` function
> 98637e08dba5 Merge pull request #136 from blogic/master
> 0a58d51052
On Tue, Jan 10, 2023 at 11:06:52PM -0800, Brian Norris wrote:
> TP-Link and ASUS OnHub devices are very similar, sharing many of the
> same characteristics and much of their Device Tree. They both run a
> version of ChromeOS for their factory firmware, and so installation
> instructions look very s
Hi,
> Can you change that?
Could you also please omit the merge commits from the listing in the commit
message?
~ Jo
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.op
On 09/12/2022 15:16, Andre Heider wrote:
Similar to ucode's print() this now prints any given values to stdout:
uhttpd.send(a, b, c, "\n");
Signed-off-by: Andre Heider
Friendly ping! Any takers?
---
ucode.c | 26 ++
1 file changed, 14 insertions(+), 12 deletions(-
After a lot of debugging & hacking I managed to make OpenWrt do 940 Mb/s
NAT on bcm53xx BCM47094:
http://lists.openwrt.org/pipermail/openwrt-devel/2022-June/038834.html
The problem I recently discovered is that NAT slowes down after enabling
WiFi. Without any actual traffic. I mean just enabling 2
On Thu, Jan 12, 2023 at 09:35:03AM -0800, Brian Norris wrote:
> Hi Christian,
>
> On Thu, Jan 12, 2023 at 6:34 AM Christian Marangi
> wrote:
> > On Tue, Jan 10, 2023 at 11:06:52PM -0800, Brian Norris wrote:
> > > diff --git a/target/linux/ipq806x/base-files/etc/board.d/01_leds
> > > b/target/li
On Thu, Jan 12, 2023 at 9:48 AM Christian Marangi wrote:
> On Thu, Jan 12, 2023 at 09:35:03AM -0800, Brian Norris wrote:
> > On Thu, Jan 12, 2023 at 6:34 AM Christian Marangi
> > wrote:
> > Downside: IIUC, this will no longer reflect in the UCI configuration,
> > and so it's less obvious how to
Hi Christian,
On Thu, Jan 12, 2023 at 6:34 AM Christian Marangi wrote:
> On Tue, Jan 10, 2023 at 11:06:52PM -0800, Brian Norris wrote:
> > diff --git a/target/linux/ipq806x/base-files/etc/board.d/01_leds
> > b/target/linux/ipq806x/base-files/etc/board.d/01_leds
> > index 2b259b903614..80a337c6a4
Hi, I got some report that user can't subscribe to the devel mailing list
and the page return
Internal Server Error
I confirmed that with a secondary email. Can someone check it?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://li
On Thu, 2023-01-12 at 21:02 +0100, Ansuel Smith wrote:
> Hi, I got some report that user can't subscribe to the devel mailing
> list
> and the page return
>
> Internal Server Error
>
> I confirmed that with a secondary email. Can someone check it?
The server was being attacked with subscribe re
On Sun, Jan 8, 2023 at 12:33 AM Linus Walleij wrote:
> I guess trying to figure out what lzma-loader does and implement
> the same for ARM is the way to go, or at some point I felt like
> implementing U-Boot for the BCM53xx and implement SEAMA
> loading from NAND in U-Boot is maybe easier...
How
Refresh target config with `make kernel_menuconfig`, then save the
result. This drops missing symbols or otherwise accounts for defaults.
It should not change any functionality.
Signed-off-by: Brian Norris
---
(no changes since v2)
Changes in v2:
* Improve description
target/linux/ipq806x/co
For IPQ8064 systems based off the "Google Storm" reference platform,
such as the TP-Link OnHub.
Signed-off-by: Brian Norris
---
(no changes since v2)
Changes in v2:
* Drop CONFIG_IPQ_LCC_806X=y, and merge CONFIG_IPQ_LCC_806X=m into this
package
* Move package to the ipq806x target
* Slim
emmc_do_upgrade() relies on identify() from the nand.sh upgrade helper.
This only works because FEATURES=emmc targets also tend to include
FEATURES=nand.
Rename identify_magic() to identify_magic_long() to match the common.sh
style and make it clear it pairs with other *_long() variants (and not,
Similar to commit 4d8b42d8a777 ("ipq40xx: point to externally compiled
dtbs in recipes").
Currently, we patch our DTS files into the kernel source tree, so the
kernel build process will produce DTBs for us. The kernel-to-DTS
dependency can cause buildroot to perform excessive rebuilds of the
kerne
TP-Link and ASUS OnHub devices are very similar, sharing many of the
same characteristics and much of their Device Tree. They both run a
version of ChromeOS for their factory firmware, and so installation
instructions look very similar to Google Wifi [1].
Things I've tested, and are working:
* E
To bring in isatty() support.
Includes new commits:
be30472bfdbb fs: add `isatty()` function
98637e08dba5 Merge pull request #136 from blogic/master
0a58d510529e nl80211: add support for NL80211_ATTR_MPATH_INFO
Signed-off-by: Brian Norris
---
Changes in v4:
* Clean up commit message
Changes
This fixes device tree registration for 'qcom,lpass-cpu' as used by
qcom-ipq8064 SoCs, and allows speaker audio to function.
This patch has been submitted (and merged, for -next; likely v6.3)
upstream.
Signed-off-by: Brian Norris
---
(no changes since v2)
Changes in v2:
* Add upstream (-next)
18 matches
Mail list logo