On Sun, Apr 16, 2023 at 12:59:49PM +0300, Arınç ÜNAL wrote:
> On 15.04.2023 20:02, Sam Kuper wrote:
>> On Fri, Mar 31, 2023 at 12:44:12PM +0300, Arınç ÜNAL wrote:
>>> These are the ideas I've been thinking about for the future of
>>> OpenWrt for a while. It looks complete enough to share it with al
On 15.04.2023 20:02, Sam Kuper wrote:
On Fri, Mar 31, 2023 at 12:44:12PM +0300, Arınç ÜNAL wrote:
These are the ideas I've been thinking about for the future of OpenWrt
for a while. It looks complete enough to share it with all of you.
[...]
https://arinc9.notion.site/OpenWrt-next-gen-ideas-6db
On Fri, Mar 31, 2023 at 12:44:12PM +0300, Arınç ÜNAL wrote:
> These are the ideas I've been thinking about for the future of OpenWrt
> for a while. It looks complete enough to share it with all of you.
> [...]
>
> https://arinc9.notion.site/OpenWrt-next-gen-ideas-6db745e7584b4823950291c96f2326bb
On 31.03.2023 20:15, Felix Fietkau wrote:
On 31.03.23 18:55, Arınç ÜNAL wrote:
On 31.03.2023 19:45, Felix Fietkau wrote:
On 31.03.23 18:40, Arınç ÜNAL wrote:
I just thought of this. Why don't we just, for example, 'make
mt7621_defconfig && make mod2noconfig', then compile normally with
kernel
On 31.03.2023 14:33, Daniel Golle wrote:
Hi!
On Fri, Mar 31, 2023 at 12:44:12PM +0300, Arınç ÜNAL wrote:
Hi all,
These are the ideas I've been thinking about for the future of OpenWrt for a
while. It looks complete enough to share it with all of you.
I'm willing to put a great deal of effort
Hi, everyone!
On Fri, 31 Mar 2023 at 22:28, Daniel Golle wrote:
>
[snipped]
> The point here is not optimization, but finding a good compromise to
> not having to compile **all** packages for **all** CPU architectures.
> The same is btw also true for MIPS and ARM targets. We pick a good
> comp
On Fri, Mar 31, 2023 at 6:50 AM Daniel Golle wrote:
>
> On Fri, Mar 31, 2023 at 03:52:47PM +0300, Arınç ÜNAL wrote:
> > On 31.03.2023 14:33, Daniel Golle wrote:
> > > Hi!
> > >
> > > On Fri, Mar 31, 2023 at 12:44:12PM +0300, Arınç ÜNAL wrote:
> > > > Hi all,
> > > >
> > > > These are the ideas I'v
On Fri, Mar 31, 2023 at 10:26:37PM +0100, Daniel Golle wrote:
> On Fri, Mar 31, 2023 at 01:34:03PM -0700, Elliott Mitchell wrote:
> > On Fri, Mar 31, 2023 at 02:47:23PM +0100, Daniel Golle wrote:
> > >
> > > Another example is selection of the rootfs. Kernel folks argue that
> > > we should use an
Off this enormous list:
https://forum.openwrt.org/t/cerowrt-ii-would-anyone-care/110554
"Matter" has begun to matter, I think. Where does openwrt stand on that?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/ma
On Fri, Mar 31, 2023 at 01:34:03PM -0700, Elliott Mitchell wrote:
> On Fri, Mar 31, 2023 at 02:47:23PM +0100, Daniel Golle wrote:
> >
> > Another example is selection of the rootfs. Kernel folks argue that
> > we should use an initramfs for that, however, we try to avoid the
> > overhead of using
On Fri, Mar 31, 2023 at 02:47:23PM +0100, Daniel Golle wrote:
>
> Another example is selection of the rootfs. Kernel folks argue that
> we should use an initramfs for that, however, we try to avoid the
> overhead of using an initramfs with it's own userland just for that.
There are two options he
On 31.03.23 18:55, Arınç ÜNAL wrote:
On 31.03.2023 19:45, Felix Fietkau wrote:
On 31.03.23 18:40, Arınç ÜNAL wrote:
I just thought of this. Why don't we just, for example, 'make
mt7621_defconfig && make mod2noconfig', then compile normally with
kernel module packages. This way, OpenWrt compile
On 31.03.2023 19:45, Felix Fietkau wrote:
On 31.03.23 18:40, Arınç ÜNAL wrote:
I just thought of this. Why don't we just, for example, 'make
mt7621_defconfig && make mod2noconfig', then compile normally with
kernel module packages. This way, OpenWrt compiles a kernel with the
least amount of ke
On 31.03.23 18:40, Arınç ÜNAL wrote:
I just thought of this. Why don't we just, for example, 'make
mt7621_defconfig && make mod2noconfig', then compile normally with
kernel module packages. This way, OpenWrt compiles a kernel with the
least amount of kernel modules (or rather, it compiles the ke
On 31.03.2023 19:35, Felix Fietkau wrote:
On 31.03.23 18:22, Arınç ÜNAL wrote:
On 31.03.2023 19:04, Felix Fietkau wrote:
On 31.03.23 14:52, Arınç ÜNAL wrote:
On 31.03.2023 14:33, Daniel Golle wrote:
Hi!
On Fri, Mar 31, 2023 at 12:44:12PM +0300, Arınç ÜNAL wrote:
Hi all,
These are the ideas
On 31.03.23 18:22, Arınç ÜNAL wrote:
On 31.03.2023 19:04, Felix Fietkau wrote:
On 31.03.23 14:52, Arınç ÜNAL wrote:
On 31.03.2023 14:33, Daniel Golle wrote:
Hi!
On Fri, Mar 31, 2023 at 12:44:12PM +0300, Arınç ÜNAL wrote:
Hi all,
These are the ideas I've been thinking about for the future of
On 31.03.2023 19:04, Felix Fietkau wrote:
On 31.03.23 14:52, Arınç ÜNAL wrote:
On 31.03.2023 14:33, Daniel Golle wrote:
Hi!
On Fri, Mar 31, 2023 at 12:44:12PM +0300, Arınç ÜNAL wrote:
Hi all,
These are the ideas I've been thinking about for the future of
OpenWrt for a
while. It looks compl
On Fri, Mar 31, 2023 at 04:18:53PM +, psv sridhar wrote:
> idiots, email looks like offcial and you are sending to un-known people.
> Thanks and Regards
Thank you for the kind advise. This is a deliberate public debate and
you are welcome to participate in any meaningful way.
> Sridhar PSVP
On 31.03.2023 18:36, Daniel Golle wrote:
On Fri, Mar 31, 2023 at 05:35:22PM +0300, Arınç ÜNAL wrote:
On 31.03.2023 16:47, Daniel Golle wrote:
On Fri, Mar 31, 2023 at 03:52:47PM +0300, Arınç ÜNAL wrote:
On 31.03.2023 14:33, Daniel Golle wrote:
Hi!
On Fri, Mar 31, 2023 at 12:44:12PM +0300, Arı
On 31.03.23 14:52, Arınç ÜNAL wrote:
On 31.03.2023 14:33, Daniel Golle wrote:
Hi!
On Fri, Mar 31, 2023 at 12:44:12PM +0300, Arınç ÜNAL wrote:
Hi all,
These are the ideas I've been thinking about for the future of OpenWrt for a
while. It looks complete enough to share it with all of you.
I'm
On Fri, Mar 31, 2023 at 05:35:22PM +0300, Arınç ÜNAL wrote:
> On 31.03.2023 16:47, Daniel Golle wrote:
> > On Fri, Mar 31, 2023 at 03:52:47PM +0300, Arınç ÜNAL wrote:
> > > On 31.03.2023 14:33, Daniel Golle wrote:
> > > > Hi!
> > > >
> > > > On Fri, Mar 31, 2023 at 12:44:12PM +0300, Arınç ÜNAL wro
Thanks Arınç for opening this discussion about improving the development
process. I would like to expand the discussion to include what, if any, changes
we'd like to make in the user experience for OpenWrt.
The first one I would propose is "Automatic renumbering of LAN in case of
conflict with
Hello there
I also don't have Notion account so will reply here to all can take note
and discuss. I have basically 2 notes:
1 - One thing that would be interesting to have it by default regarding
IPv6 is make the router to find out if it received an IPv6 address in
the WAN interface but not
On 31.03.2023 16:47, Daniel Golle wrote:
On Fri, Mar 31, 2023 at 03:52:47PM +0300, Arınç ÜNAL wrote:
On 31.03.2023 14:33, Daniel Golle wrote:
Hi!
On Fri, Mar 31, 2023 at 12:44:12PM +0300, Arınç ÜNAL wrote:
Hi all,
These are the ideas I've been thinking about for the future of OpenWrt for a
w
On Fri, Mar 31, 2023 at 03:52:47PM +0300, Arınç ÜNAL wrote:
> On 31.03.2023 14:33, Daniel Golle wrote:
> > Hi!
> >
> > On Fri, Mar 31, 2023 at 12:44:12PM +0300, Arınç ÜNAL wrote:
> > > Hi all,
> > >
> > > These are the ideas I've been thinking about for the future of OpenWrt
> > > for a
> > > wh
On 31.03.2023 14:33, Daniel Golle wrote:
Hi!
On Fri, Mar 31, 2023 at 12:44:12PM +0300, Arınç ÜNAL wrote:
Hi all,
These are the ideas I've been thinking about for the future of OpenWrt for a
while. It looks complete enough to share it with all of you.
I'm willing to put a great deal of effort
Hi!
On Fri, Mar 31, 2023 at 12:44:12PM +0300, Arınç ÜNAL wrote:
> Hi all,
>
> These are the ideas I've been thinking about for the future of OpenWrt for a
> while. It looks complete enough to share it with all of you.
>
> I'm willing to put a great deal of effort to get as much out-of-tree patch
27 matches
Mail list logo
