On Mon, Feb 05, 2024 at 08:21:43PM +0100, Rafał Miłecki wrote:
> On 5.02.2024 15:21, Daniel Golle wrote:
> > On Mon, Feb 05, 2024 at 02:23:08PM +0100, Rafał Miłecki wrote:
> > > From: Rafał Miłecki
> > >
> > > Aquantia AQR113C is PHY that needs loading a firmware. Some devices may
> > > have it s
On 5.02.2024 15:21, Daniel Golle wrote:
On Mon, Feb 05, 2024 at 02:23:08PM +0100, Rafał Miłecki wrote:
From: Rafał Miłecki
Aquantia AQR113C is PHY that needs loading a firmware. Some devices may
have it stored on flash and some need filesystem to provide it.
Are you aware of any MediaTek boa
On 5.02.2024 15:15, Robert Marko wrote:
On Mon, 5 Feb 2024 at 14:23, Rafał Miłecki wrote:
From: Rafał Miłecki
Aquantia AQR113C is PHY that needs loading a firmware. Some devices may
have it stored on flash and some need filesystem to provide it.
MediaTek holds its own AQR113C firmware file
El mar, 30 ene 2024 a las 19:16, Christian Marangi (Ansuel)
() escribió:
>
> Robert is active in OpenWrt since 2017 and with some recent stats, he
> has more than 310 commits merged in OpenWrt.
> He also have uncounted Reviewed-by tag on various PR and merged commits
> and generally helps in everyt
Have tested a few changes based on your suggestion, all of them sadly
failed:
1) Reset kernel settings to default + Remove the whole partitions block
from librerouter dts, the image fails to be compile with an error of
missing art label (probably because uno of the partitions have that label)
> On Feb 5, 2024, at 5:35 AM, Zoltan HERPAI wrote:
>
>
> One thing I fully agree with Hauke is that we should pick one (and only one)
> kernel for the next release, whenever that is. If we need to drop targets to
> achieve it (no maintainer stepping up or lack of storage on the devices), so
On Mon, Feb 05, 2024 at 02:23:08PM +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> Aquantia AQR113C is PHY that needs loading a firmware. Some devices may
> have it stored on flash and some need filesystem to provide it.
Are you aware of any MediaTek boards which do come with AQR113C but
d
On Mon, 5 Feb 2024 at 14:23, Rafał Miłecki wrote:
>
> From: Rafał Miłecki
>
> Aquantia AQR113C is PHY that needs loading a firmware. Some devices may
> have it stored on flash and some need filesystem to provide it.
>
> MediaTek holds its own AQR113C firmware file for its boards. Package it.
Hi
I do not care one whit about CIP. It will lead to redhat-style
ossification and even further delusional consideration that Linux is
"done". The Linux foundation keeps losing its way. I would prefer
OpenWrt (and arm development in particular) continue to track the
newest kernels possible and indeed,
On Sat, 3 Feb 2024, Enrico Mioso wrote:
On Sat, Feb 03, 2024 at 07:02:44PM +0100, Christian Marangi (Ansuel) wrote:
Il giorno sab 3 feb 2024 alle ore 18:55 Janusz Dziedzic
ha scritto:
sob., 3 lut 2024 o 13:08 Hauke Mehrtens napisał(a):
Hi,
I track the status of the Linux kernel 6.1 migra
Yes please.
- David
On 1/30/24 19:15, Christian Marangi (Ansuel) wrote:
Robert is active in OpenWrt since 2017 and with some recent stats, he
has more than 310 commits merged in OpenWrt.
He also have uncounted Reviewed-by tag on various PR and merged commits
and generally helps in everything r
Hi Sander,
Op zondag 4 februari 2024 om 13:35:48 +01:00:00 schreef Sander Vanheule
:
Hi Stijn,
On Sun, 2024-02-04 at 13:20 +0100, Stijn Segers wrote:
Commit daefc646e6d fixed a shell expansion issue with
zyxel-vers usage. Commit 045baca10b1 took care of this
checkpatch.pl was complaining
Hi Stijn,
On Sun, 2024-02-04 at 13:20 +0100, Stijn Segers wrote:
> Commit daefc646e6d fixed a shell expansion issue with
> zyxel-vers usage. Commit 045baca10b1 took care of this
checkpatch.pl was complaining about the format of these references, so I
amended that.
> for the rtl838x and rtl839x
> >I would choose 6.1: to get more time for some things to stabilize out and
> >because I am under the impression the kernel size is growing too fast and so
> >we are accelerating hw obsolescence.
The firmware overall size is not the only problem. Some bootloaders
might have trouble loading larg
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 ---
Am 3. Februar 2024 19:54:12 MEZ sc
On Sat, Feb 03, 2024 at 01:06:13PM +0100, Hauke Mehrtens wrote:
>
> Which kernel should we use for the next major OpenWrt release?
> We have two options and I would like to get some feedback on these:
Unless it turns out there is a pattern of people in favor of 6.1 needing
longer to respond, ther
On Sat, Feb 03, 2024 at 07:02:44PM +0100, Christian Marangi (Ansuel) wrote:
> Il giorno sab 3 feb 2024 alle ore 18:55 Janusz Dziedzic
> ha scritto:
> >
> > sob., 3 lut 2024 o 13:08 Hauke Mehrtens napisał(a):
> > >
> > > Hi,
> > >
> > > I track the status of the Linux kernel 6.1 migration in this
Il giorno sab 3 feb 2024 alle ore 18:55 Janusz Dziedzic
ha scritto:
>
> sob., 3 lut 2024 o 13:08 Hauke Mehrtens napisał(a):
> >
> > Hi,
> >
> > I track the status of the Linux kernel 6.1 migration in this github
> > issue: https://github.com/openwrt/openwrt/issues/14546
> >
> > There are still ma
sob., 3 lut 2024 o 13:08 Hauke Mehrtens napisał(a):
>
> Hi,
>
> I track the status of the Linux kernel 6.1 migration in this github
> issue: https://github.com/openwrt/openwrt/issues/14546
>
> There are still many targets on kernel 5.15 without testing support for
> kernel 6.1 in OpenWrt master. I
ssage has been wrapped
> automatically by the mailing list software.
> Date: Sat, 03 Feb 2024 17:42:22 +0100
> From: Felix Baumann
> To: openwrt-devel@lists.openwrt.org
> Subject: Re: Linux kernel 6.1 or 6.6 for OpenWrt 24.x release?
>
> Hi,
>
> from what I imagine the mainta
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,
from what I imagine the maint
Il giorno sab 3 feb 2024 alle ore 16:58 Hauke Mehrtens
ha scritto:
>
> On 2/3/24 15:31, Paul D wrote:
> > On 2024-02-03 13:06, Hauke Mehrtens wrote:
> >> Hi,
> >>
> >> I track the status of the Linux kernel 6.1 migration in this github
> >> issue: https://github.com/openwrt/openwrt/issues/14546
>
On 2/3/24 15:31, Paul D wrote:
On 2024-02-03 13:06, Hauke Mehrtens wrote:
Hi,
I track the status of the Linux kernel 6.1 migration in this github
issue: https://github.com/openwrt/openwrt/issues/14546
There are still many targets on kernel 5.15 without testing support
for kernel 6.1 in Open
On 2024-02-03 13:06, Hauke Mehrtens wrote:
Hi,
I track the status of the Linux kernel 6.1 migration in this github
issue: https://github.com/openwrt/openwrt/issues/14546
There are still many targets on kernel 5.15 without testing support for
kernel 6.1 in OpenWrt master. I assume that we nee
On Sat, 3 Feb 2024 at 13:06, Hauke Mehrtens wrote:
>
> Hi,
>
> I track the status of the Linux kernel 6.1 migration in this github
> issue: https://github.com/openwrt/openwrt/issues/14546
>
> There are still many targets on kernel 5.15 without testing support for
> kernel 6.1 in OpenWrt master. I
On 30.01.24 19:15, Christian Marangi (Ansuel) wrote:
Robert is active in OpenWrt since 2017 and with some recent stats, he
has more than 310 commits merged in OpenWrt.
He also have uncounted Reviewed-by tag on various PR and merged commits
and generally helps in everything related to IPQ (ipq806x
I know I don't have a vote, but he helped me personally port the
Mikrotik hAP AC2 ( IPQ40xx based ) platform to OpenWRT and was a huge
help in unravelling this platform.
If I could +1, I would!! Having him on the team and adding IPQ60xx
support would be amazing!
There are several platforms I'd imm
+1
Best
Nick
On 1/30/24 19:15, Christian Marangi (Ansuel) wrote:
Robert is active in OpenWrt since 2017 and with some recent stats, he
has more than 310 commits merged in OpenWrt.
He also have uncounted Reviewed-by tag on various PR and merged commits
and generally helps in everything related t
On Wed, Jan 31, 2024 at 1:35 PM Paul D wrote:
> Is this what we tested on 6846? Or this is what you've been cooking? :)
>
> I'm almost certain it's the latter.
Yeah I have it in my new patch set for the 6846, so we don't
have to unconditionally compile in the mv88e6xxx switch into all
bcm6328 ke
+1
On 2024-01-30 19:15, Christian Marangi (Ansuel) wrote:
Robert is active in OpenWrt since 2017 and with some recent stats, he
has more than 310 commits merged in OpenWrt.
He also have uncounted Reviewed-by tag on various PR and merged commits
and generally helps in everything related to IPQ
Is this what we tested on 6846? Or this is what you've been cooking? :)
I'm almost certain it's the latter.
On 2024-01-30 23:33, Linus Walleij wrote:
This adds a kernel module package for the Marvell
MV88E6XXX DSA switch and a separate module package for
the DSA tagger since it can in theory
Hi, everyone!
On Tue, 30 Jan 2024 at 18:16, Christian Marangi (Ansuel)
wrote:
>
> Robert is active in OpenWrt since 2017 and with some recent stats, he
> has more than 310 commits merged in OpenWrt.
> He also have uncounted Reviewed-by tag on various PR and merged commits
> and generally helps in
On Tue, Jan 30, 2024 at 7:16 PM Christian Marangi (Ansuel)
wrote:
>
> Robert is active in OpenWrt since 2017 and with some recent stats, he
> has more than 310 commits merged in OpenWrt.
> He also have uncounted Reviewed-by tag on various PR and merged commits
> and generally helps in everything r
Hi,
On 30.01.2024 19:15, Christian Marangi (Ansuel) wrote:
Robert is active in OpenWrt since 2017 and with some recent stats, he
has more than 310 commits merged in OpenWrt.
He also have uncounted Reviewed-by tag on various PR and merged commits
and generally helps in everything related to IPQ (
Hi!
On Wed, Jan 31, 2024 at 2:16 AM Christian Marangi (Ansuel)
wrote:
>
> Robert is active in OpenWrt since 2017 and with some recent stats, he
> has more than 310 commits merged in OpenWrt.
> He also have uncounted Reviewed-by tag on various PR and merged commits
> and generally helps in everyth
Hi,
> On Jan 30, 2024, at 19:15, Christian Marangi (Ansuel)
> wrote:
>
> Robert is active in OpenWrt since 2017 and with some recent stats, he
> has more than 310 commits merged in OpenWrt.
> He also have uncounted Reviewed-by tag on various PR and merged commits
> and generally helps in everyt
On 2024-01-31 03:15, Christian Marangi (Ansuel) wrote:
> I think Robert is a good addition to our team and would massively help
> me (Ansuel) in maintaining each IPQ target and review all the related
> PR on github and patchwork.
> I would like to add Robert to the OpenWrt committers team.
>
> The
On 1/30/24 19:15, Christian Marangi (Ansuel) wrote:
Robert is active in OpenWrt since 2017 and with some recent stats, he
has more than 310 commits merged in OpenWrt.
He also have uncounted Reviewed-by tag on various PR and merged commits
and generally helps in everything related to IPQ (ipq806x,
+1 Thanks
> On Jan 30, 2024, at 1:15 PM, Christian Marangi (Ansuel)
> wrote:
>
> Robert is active in OpenWrt since 2017 and with some recent stats, he
> has more than 310 commits merged in OpenWrt.
> He also have uncounted Reviewed-by tag on various PR and merged commits
> and generally helps
Hi,
Op dinsdag 30 januari 2024 om 19:15:54 +01:00:00 schreef Christian
Marangi (Ansuel) :
Robert is active in OpenWrt since 2017 and with some recent stats, he
has more than 310 commits merged in OpenWrt.
He also have uncounted Reviewed-by tag on various PR and merged
commits
and generally he
I do not think I get a vote, but I am deeply grateful to everyone(s)
sorting out the QCA messes.
I did not know who was doing that. Thank you very much, robert & christian.
On Tue, Jan 30, 2024 at 2:36 PM Petr Štetiar wrote:
>
> Christian Marangi (Ansuel) [2024-01-30 19:15:54]:
>
> Hi,
>
> > R
On Tue, 2024-01-30 at 19:15 +0100, Christian Marangi (Ansuel) wrote:
> Robert is active in OpenWrt since 2017 and with some recent stats, he
> has more than 310 commits merged in OpenWrt.
> He also have uncounted Reviewed-by tag on various PR and merged commits
> and generally helps in everything r
Christian Marangi (Ansuel) [2024-01-30 19:15:54]:
Hi,
> Robert is active in OpenWrt since 2017 and with some recent stats, he
> has more than 310 commits merged in OpenWrt.
> He also have uncounted Reviewed-by tag on various PR and merged commits
> and generally helps in everything related to IP
I would like to add Robert to the OpenWrt committers team.
+1
thx @robimarko for taking care of the QCA mess
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On Tue, Jan 30, 2024 at 07:15:54PM +0100, Christian Marangi (Ansuel) wrote:
> Robert is active in OpenWrt since 2017 and with some recent stats, he
> has more than 310 commits merged in OpenWrt.
> He also have uncounted Reviewed-by tag on various PR and merged commits
> and generally helps in every
On Fri, Jan 19, 2024 at 1:59 PM Tim Harvey wrote:
>
> Greetings,
>
> I've sent a v2 of my patch to add imx8m/cortexta53 support to the
> mailing list but it got caught needing moderator approval due to 'Too
> many recipients to the message' (I cc'd merely 8 people that had
> participated in the pr
On 26.01.2024 18:45, Felix Fietkau wrote:
does anybody still care about the broadcom-wl package in OpenWrt?
I think it would be nice if we could get rid of it, along with the code support
and abstraction for different wireless drivers.
It would also allow us to rewrite iwinfo in ucode with nl802
On Fri, Jan 26, 2024 at 9:56 AM INAGAKI Hiroshi
wrote:
> This is just a question: doesn't it work with "openwrt,offset"
> property of mtdsplit_uimage parser instead of modifying that parser?
It works actually...
The U-Boot takes up 3 64k erase blocks so if I just set offset to
0x3 it works l
On 1/26/24 18:45, Felix Fietkau wrote:
Hi,
does anybody still care about the broadcom-wl package in OpenWrt?
I think it would be nice if we could get rid of it, along with the code
support and abstraction for different wireless drivers.
It would also allow us to rewrite iwinfo in ucode with nl8
> Please try the latest version.
It works! Thanks for the quick fix.
d
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On 26.01.24 20:15, Dustin Howett wrote:
I am seeing this on x86/64-glibc as well.
It looks like procd is falling over in udebug_entry_vprintf at the
*second* vprintf after udebug_buf_alloc.
This appears to occur when there are log messages longer than the
minimum allocation size (128) and we tri
On Fri, Jan 26, 2024 at 06:45:58PM +0100, Felix Fietkau wrote:
> Hi,
>
> does anybody still care about the broadcom-wl package in OpenWrt?
> I think it would be nice if we could get rid of it, along with the code
> support and abstraction for different wireless drivers.
> It would also allow us to
Hi Felix,
On 1/26/24 18:45, Felix Fietkau wrote:
Hi,
does anybody still care about the broadcom-wl package in OpenWrt?
I think it would be nice if we could get rid of it, along with the code support
and abstraction for different wireless drivers.
It would also allow us to rewrite iwinfo in uco
Hello Linus,
This is just a question: doesn't it work with "openwrt,offset"
property of mtdsplit_uimage parser instead of modifying that parser?
I'm thinking like the following:
- dts:
partition@1 {
compatible = "openwrt,uimage", "denx,uimage";
reg = <0x01 0xfe>;
open
On Fri, Jan 26, 2024 at 12:21 AM Paul D wrote:
> BTW: was this what I tested in your factory and sysimages for the XG6846?
>
> If so can you roll a fresh one with this patch?
It has been used in all of them, but I made a new one on top
of the OpenWrt main branch!
https://dflund.se/~triad/krad/in
[Added the others back in Cc]
Hi Paul,
On Fri, 2024-01-26 at 00:00 +0100, Paul D wrote:
>
> So, the power budget is a global option. Do we ever envisage that parts
> of this budget can be concretely assigned to specific ports or more
> abstract ?
>
> e.g.
>
> config port
>
The simple past tense of offset is... offset :)
Suggested: Split also after offset uImage
BTW: was this what I tested in your factory and sysimages for the XG6846?
If so can you roll a fresh one with this patch? Then I can give you a
more recent Tested-By:
On 2024-01-23 23:17, Linus Walle
So, the power budget is a global option. Do we ever envisage that parts
of this budget can be concretely assigned to specific ports or more
abstract ?
e.g.
config port
option name 'lan8'
option id '1'
option enable '1'
On Wed, Jan 24, 2024 at 8:32 PM Álvaro Fernández Rojas
wrote:
> I tested this:
> - Comtrend AR-5381u (bcm6328 with internal switch only).
> - Netgear DGND3700v2 (bcm6362 with external BCM53125 switch).
> And there were no regressions on any of them.
>
> So I merged it @ 3cf1fe5508ee8a2a2c6e33a829
Hi Linus,
I tested this:
- Comtrend AR-5381u (bcm6328 with internal switch only).
- Netgear DGND3700v2 (bcm6362 with external BCM53125 switch).
And there were no regressions on any of them.
So I merged it @ 3cf1fe5508ee8a2a2c6e33a829bfb6c81381ccd0
https://git.openwrt.org/?p=openwrt/openwrt.git;a=
Hi,
On Mon, 22 Jan 2024 at 21:27, Tim Harvey wrote:
>
> Greetings,
>
> What is the best known method to add items to config-$KVER when you
> have subtargets with individual config-default files - specifically
> how are the items in this file ordered properly? Maybe the norm is to
> put them alpha
Hi,
On 23.01.24 10:54, G10h4ck wrote:
Hi all!
At Altermundi we have been (mostly silently) advancing with LibreRouter
2 project, we have now some prototype at hand and started testing also
radios, we need that the radio works good with OpenWrt and that at least
have good 802.11s support in the
et antoher USB crap? optionally -
may be, but standart barrel plug 5.5/2.1 + (optional internal JST HX 2.54mm 2P
connector) is better.
> * Expansion slots: mikroBUS
> * Certification: FCC/EC/RoHS compliance
> * Case: PCB size is compatible to BPi-R4 and the case design can be re-used
> * JTAG
Sorry for the noise, it was physical connection issue. Now I see it
works correctly:
[8.360566] mhi mhi0: Wait for device to enter SBL or Mission mode
[8.475137] kmodloader: done loading kernel modules from /etc/modules.d/*
[8.482058] ath11k_pci :01:00.0: chip_id 0x0 chip_family 0x
On Wed, 2024-01-10 at 16:59 +0100, Tomasz Maciej Nowak wrote:
> 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
śr., 17 sty 2024 o 18:15 Daniel Golle napisał(a):
>
> On Wed, Jan 17, 2024 at 05:47:26PM +0100, John Crispin wrote:
> >
> > On 17.01.24 17:46, Janusz Dziedzic wrote:
> > > Do you think I can use m.2 A->M converter here and use wifi mt7916 A+E
> > > (6GHz) instead of NVMe?
> > > Eg.https://kamami.p
I did look into the EU CRA from the commercial entity point-of-view.
SBOM documentation and continued product monitoring for vulnerabilities
and hazards to people are central + effective incident response
(including; how to pull a product of the market if needed).
In regard to OpenWrt One; it
On Fri, Jan 19, 2024 at 09:18:02PM +0100, Hauke Mehrtens wrote:
> The EU is working on a EU Cyber Resilience Act to improve the software
> security of (consumer) software and (consumer) hardware which contains
> software. This should be similar to the CE sign, but for software.
> https://en.wikiped
The EU is working on a EU Cyber Resilience Act to improve the software
security of (consumer) software and (consumer) hardware which contains
software. This should be similar to the CE sign, but for software.
https://en.wikipedia.org/wiki/Cyber_Resilience_Act
After the successful lobbying of mu
If there is no objection I’d go ahead and merge this?
https://github.com/openwrt/openwrt/pull/14426
* busybox: enable sha hash for /etc/shadow
* busybox: switch to sha256 for passwd
Best,
Paul
> On Jan 19, 2024, at 08:38, abnoeh wrote:
>
> sorry, use_bcrypt isn't something in mainline busybo
Ivan Ivanov writes:
> blobless ath9k
OK, I'll bite.
Get yourself a microscope and look closer at that chip. You might find
some code in there, even if the driver didn't load any. Please ask
Qualcomm for the source and come back when you've got it.
Modern systems contain a large number of bin
Dear community,
This is an excellent idea by Dave Taht to use multiple ath9k chips.
Actually, I don't understand: how for a "modern, open, stable" WiFi
platform - someone could suggest a blobbed Mediatek or even worse,
Broadcom. an OpenWRT official device should be no worse than
LibreCMC-supported
Hi Tim,
> I seem to recall a way to ask OpenWrt's build system to output a list
> of all variable values used in the build but can't find it documented
> or in my notes. Does anyone know how to do that?
>
> Also, is there a way to output a post-processed Makefile after all the
> define foo gets d
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 ---
On 2024-01-17 16:21, John Crispin
sorry, use_bcrypt isn't something in mainline busybox but a patched
vesrion so I think sha256 is best option here
2024-01-19 오후 4:28에 abnoeh 이(가) 쓴 글:
that option only applies if we use busybox internal crypt,
BUSYBOX_DEFAULT_USE_BB_CRYPT is set but we don't so it doesn't needed
(it's using musl
that option only applies if we use busybox internal crypt,
BUSYBOX_DEFAULT_USE_BB_CRYPT is set but we don't so it doesn't needed
(it's using musl here)
you'd need to change this option (line 1367) on same file
config BUSYBOX_DEFAULT_FEATURE_DEFAULT_PASSWD_ALGO
string
default "md5
> On Jan 18, 2024, at 12:11 PM, Dave Taht wrote:
>
> OpenWrt One could use a logo...
Could we get the designer of the current OpenWrt logo/wordmark to augment it
with the word "One"?
See:
https://github.com/openwrt/branding/blob/master/logo/openwrt_logo_text_horizontal_blue_and_dark_blue.sv
On 1/18/24 12:01, Tim Harvey wrote:
Greetings,
I seem to recall a way to ask OpenWrt's build system to output a list
of all variable values used in the build but can't find it documented
or in my notes. Does anyone know how to do that?
Also, is there a way to output a post-processed Makefile af
On 1/18/24 10:37, Chuanhong Guo wrote:
MT7981 is such a chip with NAT offload capability, and the
flow-offload driver mentioned in other threads is actually
a driver for this hardware block.
Since it's a cost-down MT7986 I would imagine this particular
feature is the same between them:
HW NAT
−
On Thu, Jan 18, 2024 at 12:04 PM Gregers Baur-Petersen wrote:
>
>
>
> On 18/01/2024 17.50, Dave Taht wrote:
> > tee-hee. For the record, I would prefer less (and less buggy) offloads
> > than offloads, and to work on scaling software better to multi-cores.
I had heard there was a mt76? mt79? feat
On 18/01/2024 17.50, Dave Taht wrote:
tee-hee. For the record, I would prefer less (and less buggy) offloads
than offloads, and to work on scaling software better to multi-cores.
I also would love to find a chip where fq_codel could be offloaded,
but with open source for the offload, since the
tee-hee. For the record, I would prefer less (and less buggy) offloads
than offloads, and to work on scaling software better to multi-cores.
I also would love to find a chip where fq_codel could be offloaded,
but with open source for the offload, since the nss drivers are
slightly broken...
I als
Hi!
On Fri, Jan 19, 2024 at 12:23 AM Fernando Frediani wrote:
>
> Hi, interesting. Is it enough to give it the necessary performance boost
> when doing NAT ? Is it capable of doing it on the chip or does it do on
> the CPU ? Reading about it seems to be a software thing although seems
> there are
Hi,
you will also need to enable additional ciphers in musl libc (disabling the
crypt size hack).
Please disregard that remark, it has already been pointed out that the hack is
disabled by default since quite some time.
~ Jo
___
openwrt-devel m
Hi,
Does the following do the trick?
you will also need to enable additional ciphers in musl libc (disabling the
crypt size hack).
~ Jo
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/open
Hi,
> however Busybox doesn't configed to use those and still use md5 as
> default, while we bring other hash algos into flash anyway:
Does the following do the trick?
diff --git a/package/utils/busybox/Config-defaults.in
b/package/utils/busybox/Config-defaults.in
index b3c3f9a0b2..5ae8dd5622 1
On 17.01.24 20:31, David Bauer wrote:
Hi John,
On 1/9/24 11:49, John Crispin wrote:
FAQ
* Why are there are 2 different flash chips?
- the idea is to make the device (almost!) unbrickable and very easy
to recover
- NAND will hold the main loader (U-Boot) and the Linux image and
will be the
Hi John,
On 1/9/24 11:49, John Crispin wrote:
FAQ
* Why are there are 2 different flash chips?
- the idea is to make the device (almost!) unbrickable and very easy to recover
- NAND will hold the main loader (U-Boot) and the Linux image and will be the
default boot device
- NOR will be write-p
On 17.01.24 20:28, Daniel Santos wrote:
On 1/16/24 00:36, John Crispin wrote:
And in the interest of running *my* own mouth, I'm stoked as hell --
LOVE that it will have mikroBUS! Thanks to John and everyone working
on this!
My only request is that any unused gpios that don't make it to
m
On 1/16/24 00:36, John Crispin wrote:
And in the interest of running *my* own mouth, I'm stoked as hell --
LOVE that it will have mikroBUS! Thanks to John and everyone working
on this!
My only request is that any unused gpios that don't make it to
mikroBUS find their way to a (possibly unpo
On Wed, Jan 17, 2024 at 05:47:26PM +0100, John Crispin wrote:
>
> On 17.01.24 17:46, Janusz Dziedzic wrote:
> > Do you think I can use m.2 A->M converter here and use wifi mt7916 A+E
> > (6GHz) instead of NVMe?
> > Eg.https://kamami.pl/akcesoria-do-raspberry-pi/587051-m2-m-key-to-m2-a-key-adapter-
On 17.01.24 17:19, Fernando Frediani wrote:
Hi, again, does this SoC have any type of NAT offload capability ? Now
a days with common Internet Broadband plans that is becoming a must.
Also is there any possibility to consider more than just 2 Ethernet
ports (at least 4)? Would that increase
śr., 17 sty 2024 o 16:27 John Crispin napisał(a):
>
> Additional FAQ for OpenWrt One
>
> This is a summary of some further questions regarding the OpenWrt One
> project gathered so far. After OpenWrt voted to move forward, it will be
> converted into a page within the OpenWrt wiki as a place for c
On 17.01.24 17:46, Janusz Dziedzic wrote:
Do you think I can use m.2 A->M converter here and use wifi mt7916 A+E
(6GHz) instead of NVMe?
Eg.https://kamami.pl/akcesoria-do-raspberry-pi/587051-m2-m-key-to-m2-a-key-adapter-m2-m-key-do-m2-a-key.html
Will that work?
so the theory but we wont know u
Additional FAQ for OpenWrt One
This is a summary of some further questions regarding the OpenWrt One
project gathered so far. After OpenWrt voted to move forward, it will be
converted into a page within the OpenWrt wiki as a place for collecting
the latest information.
Q: Will the various ha
On Thu, Dec 07, 2023 at 01:23:01PM +, Petr Štetiar wrote:
> Varadarajan Narayanan [2023-12-07 15:29:23]:
>
> Hi,
>
> > SoC : QCOM IPQ9574
> > RAM : 2GB DDR4
> > Flash : eMMC 8GB
> > WiFi: 1 x 2.4GHz
> > 1 x 5GHz
> > 1 x 6GHz
>
> BTW it doesn't
On Thu, Dec 07, 2023 at 11:11:03AM +0100, Robert Marko wrote:
>
> On 07. 12. 2023. 10:59, Varadarajan Narayanan wrote:
> > SoC : QCOM IPQ9574
> > RAM : 2GB DDR4
> > Flash : eMMC 8GB
> > WiFi: 1 x 2.4GHz
> > 1 x 5GHz
> > 1 x 6GHz
> >
> > Sign
> Interesting idea. We've been making and maintaining OpenWrt based
> routers (yes with our little additions on top) for over a decade. Seems
> like you have everything figured out already, but wanted to state the
> obvious anyway - if you are interested, we are here and we would be
> happy to
On Sat, Jan 13, 2024 at 5:26 PM Lech Perczak wrote:
>
> W dniu 2024-01-08 o 22:25, Tim Harvey pisze:
> > copy 5.15 patches excluding some that need manual rework touching
> > non-upstream led props.
> >
> > Signed-off-by: Tim Harvey
> > ---
> > .../linux/imx/patches-6.1/100-bootargs.patch | 11
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,
Interesting idea. We've been
501 - 600 of 20037 matches
Mail list logo
