On Tue, Oct 24, 2023 at 02:21:35PM +0200, Bjørn Mork wrote:
> Christian Marangi writes:
>
> > Anyway I have also found this [1]... if it does actually works, it might be
> > THE solution to our specific problem. Wonder if someone can test it on a
> > sample repository.
> >
> > [1]
On Sun, Oct 29, 2023 at 07:25:38AM +0200, Stijn Tintel wrote:
> On 24/10/2023 15:25, Christian Marangi wrote:
> > On Tue, Oct 24, 2023 at 02:21:35PM +0200, Bjørn Mork wrote:
> >> Christian Marangi writes:
> >>
> >>> Anyway I have also found this [1]... if it does actually works, it might
> >>>
Many devices do not have hardware random number generators. Yet
more do than don't, and they are becoming more common.
Signed-off-by: Elliott Mitchell
---
v2: As requested, since there is a dislike of =n even though it
works fine with all tools.
---
target/linux/airoha/config-5.15
have been squeezed out of x32 for it
to be release-worthy. Yet it seems appropriate to try to get an
experimental build operational. The patch merely enables kernel support,
I expect userspace to take some time.
Elliott Mitchell (10):
kernel: change CONFIG_HW_RANDOM default to y
kernel/gener
This option is automatically enabled by CONFIG_FB=y. There is no
reason to specifically enable it.
Signed-off-by: Elliott Mitchell
Reviewed-by: Philip Prindeville 04/2023
---
target/linux/generic/config-5.15 | 1 -
target/linux/generic/config-6.1 | 1 -
2 files changed, 2 deletions(-)
diff
-by: Elliott Mitchell
---
I suggest OpenWRT should place some effort towards x86-x32. x86-x32
seems a rather superior generic target for OpenWRT. Only issue is
it could be valuable to have at least minimal amd64 userland support
alongside the x86-x32 version.
Note, this simply enables kernel
All of the sublevels choose their own values, so there is no point
in the common file having anything. This also removes a warning from
the kernel build process.
Signed-off-by: Elliott Mitchell
Reviewed-by: Philip Prindeville 04/2023
---
target/linux/x86/config-5.15 | 2 +-
target
The SCx200 is part of the Geode platform. As such generic x86
doesn't need the driver, but Geode does.
Signed-off-by: Elliott Mitchell
Reviewed-by: Philip Prindeville 04/2023
---
target/linux/x86/config-5.15 | 5 +
target/linux/x86/config-6.1| 5 +
target/linux/x86/geode
Quite reasonable to have support for the Geode HW random number
generator. On the Geode kernel.
Support for the VIA HWRNG has been enabled in common. Pull that
from the Geode kernel.
Signed-off-by: Elliott Mitchell
Reviewed-by: Philip Prindeville 04/2023
---
target/linux/x86/config-5.15
There is no point in attempting to set CONFIG_FS_MBCACHE. The way
the Kconfig files are setup, your choice will be overridden. As
such there isn't any point in documenting a default.
Signed-off-by: Elliott Mitchell
---
target/linux/archs38/config-5.15 | 1 -
target/linux/armsr
While functional and small during its time, ext2 support should no
longer be enabled by default. For most purposes aside from memory
footprint, ext4 is rather superior. Time to play Taps.
Signed-off-by: Elliott Mitchell
---
I haven't done builds to confirm the size delta. I suspect it won't
The i915 chipset was mostly for ia32 Intel P4 processors. While
these could reasonably be called legacy due to not being amd64, they
don't fit the profile for OpenWRT's x86/legacy configuration. Leave
i915 support enabled with the generic configuration.
Signed-off-by: Elliott Mitchell
These spots should be detecting the amd64 architecture, not the
specific target name. If additional amd64 targets were added, or
the target was renamed, these would fail to build.
Signed-off-by: Elliott Mitchell
---
package/firmware/intel-microcode/Makefile | 2 +-
package/kernel/linux/modules
On Tue, Oct 24, 2023 at 02:25:06PM +0200, Christian Marangi wrote:
> On Tue, Oct 24, 2023 at 02:21:35PM +0200, Bjørn Mork wrote:
> > Christian Marangi writes:
> >
> > > Anyway I have also found this [1]... if it does actually works, it might
> > > be
> > > THE solution to our specific problem.
Differences between source code handling systems have some influence on
development approach. Some approaches which work well in one version
control systems work poorly in others. Due to this I would like to
highlight one technique which works extremely poorly in Git.
Different Linux kernel
On Tue, Mar 14, 2023 at 03:23:11PM -0300, Luiz Angelo Daros de Luca wrote:
>
> Yes, docs are quite outdated, mostly because everything now runs out
> of the box. The x86/64 target does not have the embedded restrictions
> in mind and the kernel has all VM drivers for most hypervisors
> built-in
These spots should be detecting the amd64 architecture, not the
specific target name. If additional amd64 targets were added, or
the target was renamed, these would fail to build.
Signed-off-by: Elliott Mitchell
---
package/firmware/intel-microcode/Makefile | 2 +-
package/kernel/linux/modules
While many Intel P4 processors were produced, they do not represent
sufficient share of x86 to deserve an exclusive target. i686 is
a much larger share. Due to the feature of SMP, which was absent
from x86 before i686 this is still worthy of a distinct target.
Signed-off-by: Elliott Mitchell
There are few (if any) non-64-bit x86 processors currently in
production, therefore calling non-64-bit "generic" is a major
misnomer.
Signed-off-by: Elliott Mitchell
---
package/kernel/linux/modules/virt.mk| 2 +-
target/linux/x8
Point "generic" at amd64 which is far more important to nearly
everyone.
Signed-off-by: Elliott Mitchell
---
package/kernel/linux/modules/virt.mk| 2 +-
target/linux/x86/Makefile | 2 +-
.../x86/{64 => generic}/b
ough a x86 "generic" should
NOT point at non-amd64.
Elliott Mitchell (4):
packages/x86: detect architecture, not x86/64 target
kernel/x86: revert "generic" to i686 ("Pentium Pro")
kernel/x86: rename "generic" to i686
kernel/x86: move "64"
When reading https://openwrt.org/docs/guide-user/virtualization/start it
is clear this hasn't seen much love. Several portions seemed to
exclusively target developers and not really be meant for serious use.
As such I was unsurprised to discover:
While some older PCI motherboard might emulate some functions via
ISA, actual ISA is absent from anything non-legacy. Move ISA DMA
enabling to Geode and Legacy.
Signed-off-by: Elliott Mitchell
---
Question here is how far to go with removing ISA support? Certainly it
is appropriate to keep
On Thu, Apr 27, 2023 at 12:50:52AM +0200, Stefan Lippers-Hollmann wrote:
> On 2023-04-19, Elliott Mitchell wrote:
> > Direct Rendering Manager is mainly for running X (possibly Wayland
> > too). As OpenWRT is meant for networking devices, there is no need
> > for the
-by: Elliott Mitchell
---
I suggest OpenWRT should be placing quite a bit of effort towards
x86-x32. x86-x32 seems a rather superior generic target for OpenWRT.
Only issue is it could be valuable to have at least minimal amd64
userland support alongside the x86-x32 version.
---
target/linux/x86/64
All of the sublevels choose their own values, so there is no point
in the common file having anything. This also removes a warning from
the kernel build process.
Signed-off-by: Elliott Mitchell
---
target/linux/x86/config-5.10 | 2 +-
target/linux/x86/config-5.15 | 2 +-
target
Well, was a specific objective ever chosen for the x86 version of
OpenWRT?
I can state my goal/hope for OpenWRT/x86. The *WRT Linux distributions
were so named for originally targeting the LinkSys WRT54G. This was a
small AP, so one might expect builds to be for small APs. By today's
standards
I propose changing how kernel configuration files are handled in Git.
Specifically, I propose all targets on the development branch should
*always* have "config-" and "config-" files. When
development moves off the older kernel, the configuration file should be
kept until the configuration file
Quite reasonable to have support for the Geode HW random number
generator. On the Geode kernel.
Support for the VIA HWRNG has been enabled in common. Pull that
from the Geode kernel.
Signed-off-by: Elliott Mitchell
---
target/linux/x86/config-5.10 | 1 -
target/linux/x86/config-5.15
I don't know what version of Linux this option disappeared at, but
it is clearly gone now.
Signed-off-by: Elliott Mitchell
---
target/linux/generic/config-5.10 | 1 -
target/linux/generic/config-5.15 | 1 -
2 files changed, 2 deletions(-)
diff --git a/target/linux/generic/config-5.10 b/target
The SCx200 is part of the Geode platform. As such generic x86
doesn't need the driver, but Geode does.
Signed-off-by: Elliott Mitchell
---
target/linux/x86/config-5.10 | 5 +
target/linux/x86/config-5.15 | 5 +
target/linux/x86/geode/config-5.10 | 3 +++
target/linux/x86
Direct Rendering Manager is mainly for running X (possibly Wayland
too). As OpenWRT is meant for networking devices, there is no need
for the support to be present.
Signed-off-by: Elliott Mitchell
---
target/linux/x86/64/config-5.10 | 40
target/linux/x86/64
OpenWRT is not a graphics-oriented Linux distribution. There is no
need for AGP support in any standard OpenWRT kernel.
Signed-off-by: Elliott Mitchell
---
target/linux/x86/64/config-5.10 | 5 -
target/linux/x86/64/config-5.15 | 5 -
target/linux/x86/generic/config-5.10
On Thu, Apr 27, 2023 at 01:11:13AM +0200, Stefan Lippers-Hollmann wrote:
> On 2023-04-26, Elliott Mitchell wrote:
> [...]
> >
> > Looks like little of ISA remained on "64", yet some DMA support remained
> > due to the generic configuration. Remove the ISA an
Many devices do not have hardware random number generators. Yet
more do than don't, and they are becoming more common.
Signed-off-by: Elliott Mitchell
---
target/linux/airoha/config-5.15 | 1 -
target/linux/apm821xx/config-5.10 | 1 -
target/linux/apm821xx/config-5.15
All of the sublevels choose their own values, so there is no point
in the common file having anything. This also removes a warning from
the kernel build process.
Signed-off-by: Elliott Mitchell
---
target/linux/x86/config-5.10 | 2 +-
target/linux/x86/config-5.15 | 2 +-
2 files changed, 2
On Thu, Apr 27, 2023 at 12:46:49AM +0200, Stefan Lippers-Hollmann wrote:
>
> On 2023-03-30, Elliott Mitchell wrote:
> > Full amd64 support isn't really appropriate for most situations
> > OpenWRT is deployed. Whereas x86-x32 seems extremely appropriate for
> > these sit
The SCx200 is part of the Geode platform. As such generic x86
doesn't need the driver, but Geode does.
Signed-off-by: Elliott Mitchell
---
target/linux/x86/config-5.10 | 5 +
target/linux/x86/config-5.15 | 5 +
target/linux/x86/geode/config-5.10 | 3 +++
target/linux/x86
On Tue, Apr 25, 2023 at 04:23:20PM -0700, Elliott Mitchell wrote:
> I don't know what version of Linux this option disappeared at, but
> it is clearly gone now.
Then when I try to find it again
(`find build_dir/target-$targ/linux-$targ/linux-5.15.108 -name Kconfig\*
-print0 | xargs -
t OpenWRT's target embedded network devices? This is something
needed for a graphics desktop, not an embedded networking devices (unless
you're trying to create X-terminals). As such this also seems like a
misfit for OpenWRT/x86.
Elliott Mitchell (9):
kernel/generic: remove CONFIG_FB_NOTIFY
ke
On Thu, Apr 27, 2023 at 05:38:18AM +0200, Stefan Lippers-Hollmann wrote:
> On 2023-04-26, Elliott Mitchell wrote:
> > On Thu, Apr 27, 2023 at 01:11:13AM +0200, Stefan Lippers-Hollmann wrote:
> > > On 2023-04-26, Elliott Mitchell wrote:
> > > [...]
> > > >
&g
On Thu, Apr 27, 2023 at 05:04:36AM +0100, Joseph Mullally wrote:
> One nice feature for users of the "x86/64" and similar builds are that
> they work out of the box on most generic hardware or virtualization
> platforms. I use it on real hardware and KVM with device passthrough,
> and it was very
On Fri, Apr 28, 2023 at 12:04:15PM -0600, Philip Prindeville wrote:
>
> > On Apr 26, 2023, at 2:17 PM, Elliott Mitchell wrote:
> >
> > Well, was a specific objective ever chosen for the x86 version of
> > OpenWRT?
>
> Does it need one? As the most ubiquitous
On Fri, Apr 28, 2023 at 11:00:43AM -0600, Philip Prindeville wrote:
> My own experience disagrees.
>
> I spent 17 months bringing up a Xeon-D based traffic shaper for 40Gb/s of
> traffic in a radio base station.
>
> And yes, when collected crunched traffic statistics, it did use more than 4GB
On Thu, Apr 27, 2023 at 11:27:30AM +0200, Thibaut wrote:
>
> > Le 27 avr. 2023 à 02:00, Elliott Mitchell a écrit :
> >
> > On Thu, Apr 27, 2023 at 12:46:49AM +0200, Stefan Lippers-Hollmann wrote:
> >
> >> While I might understand (understand, not support) a
On Thu, Apr 27, 2023 at 11:21:28AM +0200, Thibaut wrote:
>
> > Le 27 avr. 2023 à 02:11, Elliott Mitchell a écrit :
> >
> > On Thu, Apr 27, 2023 at 12:50:52AM +0200, Stefan Lippers-Hollmann wrote:
> >> On 2023-04-19, Elliott Mitchell wrote:
> >>> Direct
onfig-5.15, why isn't that staying unchanged?
I'm guessing you're unaware of a subtlety of how the .config system
actually works. Take a second look, some handy examples:
> > On Apr 22, 2023, at 11:46 AM, Elliott Mitchell wrote:
> > diff --git a/target/linux/armvirt/32/config-5.10
&g
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
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 arg
run `renice` on them later. This makes benchmarks better guides.
On Mon, Apr 03, 2023 at 09:12:47PM +0200, Paul Oranje wrote:
>
> > Op 3 apr. 2023, om 00:28 heeft Elliott Mitchell het
> > volgende geschreven:
> >
> > Am I the only person who finds commit 3efd49a5
On Fri, Apr 07, 2023 at 12:39:09AM +0300, Sergey Ponomarev wrote:
> The WebDAV is an extension for HTTP for shared folders.
> In order to make wget working with it we have to declare the missing
> constants with methods.
> They don't take part in a logic except of OPTIONS methods that can't have
the same type
(failure) and has the end being different. Whereas this one, one early
return is success and most are failures.
Notable request_types[ARRAY_SIZE(request_types)] is an invalid entry.
This is a presently harmless bug.
Overall not a bad idea, just some patch issues.
If you use either
On Fri, Apr 07, 2023 at 12:39:08AM +0300, Sergey Ponomarev wrote:
> Only GET and HEAD shouldn't have a body
>
> Signed-off-by: Sergey Ponomarev
Still kind of on the short side. Also doesn't exactly describe what the
patch is doing.
> @@ -292,14 +292,7 @@ static void
Am I the only person who finds commit 3efd49a588
("tools/squashfs4: enable parallel builds") a bit odd? Specifically from
the commit message:
> Run `time make tools/squashfs4/{clean,compile} -j$(nproc)`
> Before:
> real0m8.803s
> user0m12.415s
> sys 0m1.317s
> After:
> real
On Tue, May 02, 2023 at 02:45:43AM +0200, Alberto Bursi wrote:
>
>
> On 26/04/23 22:17, Elliott Mitchell wrote:
> > Well, was a specific objective ever chosen for the x86 version of
> > OpenWRT?
> >
> > I can state my goal/hope for OpenWRT/x86. The *WRT Linu
On Thu, May 04, 2023 at 03:50:05AM +0100, Daniel Golle wrote:
> On Wed, May 03, 2023 at 06:36:10PM -0700, Elliott Mitchell wrote:
> > On Tue, May 02, 2023 at 02:45:43AM +0200, Alberto Bursi wrote:
> > >
> > >
> > > On 26/04/23 22:17, Elliott Mitchell wrote:
&g
On Fri, May 05, 2023 at 02:43:08AM +0100, Joseph Mullally wrote:
> On Thu, May 4, 2023 at 7:35 AM Elliott Mitchell wrote:
> >
> > The last generic OpenWRT x86 5.15 image I built less than a week ago
> > produced a roughly 28MB vmlinux.bin file. Some of that disappears sin
On Wed, Apr 26, 2023 at 01:14:54PM -0700, Elliott Mitchell wrote:
> I propose changing how kernel configuration files are handled in Git.
> Specifically, I propose all targets on the development branch should
> *always* have "config-" and "config-" files. When
>
On Sat, Feb 03, 2024 at 11:21:45AM -0800, Elliott Mitchell wrote:
> 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:
Create a script for automating kernel version changes. This
generates a pair of commits which cause history to remain attached
to all versioned configuration files.
Signed-off-by: Elliott Mitchell
---
scripts/kernel_upgrade.pl | 191 ++
1 file changed, 191
On Wed, Feb 14, 2024 at 10:03:00AM +0100, Rafał Miłecki wrote:
> On 7.02.2024 02:16, Elliott Mitchell wrote:
> > diff --git a/scripts/kernel_upgrade.pl b/scripts/kernel_upgrade.pl
> > new file mode 100755
> > index 00..b9fe5882a3
> > --- /dev/null
> >
On Tue, Feb 06, 2024 at 05:16:41PM -0800, Elliott Mitchell wrote:
> Create a script for automating kernel version changes. This
> generates a pair of commits which cause history to remain attached to
> all versioned configuration files.
>
> Crucially this makes `git blame` work
On Wed, Feb 07, 2024 at 11:53:55AM +0100, Jonas Gorski wrote:
> On Wed, 7 Feb 2024 at 02:48, Elliott Mitchell wrote:
> >
> > Create a script for automating kernel version changes. This
> > generates a pair of commits which cause history to remain attached
> > to all ve
*everything*, which greatly simplifies rebasing patches
which effect multiple devices.
Signed-off-by: Elliott Mitchell
---
v2:
Major tweaking. No longer try to do `git merge --ff-only `,
but instead advise user to do so.
Add usage message.
Add statement about strategy.
Adjust commit messages
On Wed, Dec 13, 2023 at 01:59:07PM +0100, Martin Schiller wrote:
> On 2023-12-13 02:45, Elliott Mitchell wrote:
> >
> > No idea, I wasn't able to find very much information when I looked at
> > this.
> >
> > I did find:
> > https://lists.openwrt.org/pip
On Sat, Nov 25, 2023 at 09:36:33AM -0800, Elliott Mitchell wrote:
> On Sat, Nov 25, 2023 at 07:08:20AM +0100, Felix Fietkau wrote:
> > On 25.11.23 03:28, Elliott Mitchell wrote:
> >
> > Since there is no perfect solution, there are always some trade-offs
> > involv
On Thu, Dec 14, 2023 at 10:38:34AM +0100, Jonas Gorski wrote:
> On Wed, 13 Dec 2023 at 23:55, Elliott Mitchell wrote:
> >
> > If my belief no one is using CONFIG_PINCTRL on a Geode platform is
> > correct, then the original patch is correct. From examination of the
>
On Tue, Dec 12, 2023 at 04:48:32PM +0100, Jonas Gorski wrote:
>
> On Sun, 10 Dec 2023 at 18:49, Elliott Mitchell wrote:
> >
> > Date: Tue, 25 Apr 2023 16:23:20 -0700
> >
> > This option is automatically enabled by CONFIG_FB=y. There is no
> > reason to specif
On Tue, Dec 12, 2023 at 04:54:05PM +0100, Jonas Gorski wrote:
>
> On Sun, 10 Dec 2023 at 18:51, Elliott Mitchell wrote:
> >
> > Date: Fri, 3 Nov 2023 22:57:43 -0700
> >
> > Enabling an Intel chipset feature on a platform originally made by
> > National S
On Fri, Dec 08, 2023 at 06:53:31PM +0100, Thibaut wrote:
>
> > Le 8 déc. 2023 à 16:39, Elliott Mitchell a écrit :
> >
> > On Fri, Dec 08, 2023 at 11:14:38AM +0100, Robert Marko wrote:
> >> On Fri, 8 Dec 2023 at 11:13, Piotr Dymacz wrote:
> >>>
&g
There is a desire to reduce the time spent on x86 OpenWRT platforms.
"generic" is most suitable for removal. The few systems which could
use "generic" must now opt for "legacy" (or for a lucky few "64").
Signed-off-by: Elliott Mitchell
---
target/linu
popular due to power
consumption and poor performance.
Elliott Mitchell (1):
kernel/x86: merge "generic" into "legacy"
target/linux/x86/Makefile | 2 +-
target/linux/x86/generic/config-6.1 | 508 --
target/linux/x86/generic/target.mk
Date: Tue, 25 Apr 2023 16:23:20 -0700
This option is automatically enabled by CONFIG_FB=y. There is no
reason to specifically enable it.
Signed-off-by: Elliott Mitchell
Reviewed-by: Philip Prindeville 04/2023
---
target/linux/generic/config-5.15 | 1 -
target/linux/generic/config-6.1 | 1
of cleanup done sooner, rather than later
would be helpful.
Elliott Mitchell (11):
kernel: change CONFIG_HW_RANDOM default to y
kernel/generic: remove CONFIG_FB_NOTIFY
kernel: purge CONFIG_FS_MBCACHE
kernel: remove ext2 support from kernel
kernel/x86: remove CONFIG_HDMI
Revert "x86/
Date: Sat, 22 Apr 2023 10:46:30 -0700
Many devices do not have hardware random number generators. Yet
more do than don't, and they are becoming more common.
Signed-off-by: Elliott Mitchell
---
v2: As requested, since there is a dislike of =n even though it
works fine with all tools
Date: Tue, 9 May 2023 13:57:31 -0700
While functional and small during its time, ext2 support should no
longer be enabled by default. For most purposes aside from memory
footprint, ext4 is rather superior. Time to play Taps.
Signed-off-by: Elliott Mitchell
---
I haven't done builds
Date: Tue, 9 May 2023 14:36:00 -0700
There is no point in attempting to set CONFIG_FS_MBCACHE. The way
the Kconfig files are setup, your choice will be overridden. As
such there isn't any point in documenting a default.
Signed-off-by: Elliott Mitchell
---
target/linux/archs38/config-5.15
Date: Fri, 3 Nov 2023 22:57:43 -0700
Enabling an Intel chipset feature on a platform originally made by
National Semiconductor and later bought by AMD. Could we cut the Intel
enthusiasm?
This reverts commit 4eda2fddf2995c8ade2b1e0faddc8ce1f1e0ec5f.
Signed-off-by: Elliott Mitchell
---
target
Date: Wed, 19 Apr 2023 14:07:47 -0700
Quite reasonable to have support for the Geode HW random number
generator. On the Geode kernel.
Signed-off-by: Elliott Mitchell
---
target/linux/x86/config-5.15 | 1 -
target/linux/x86/config-6.1| 1 -
target/linux/x86/geode/config-5.15 | 1
Date: Thu, 13 Apr 2023 17:07:20 -0700
The SCx200 is part of the Geode platform. As such generic x86
doesn't need the driver, but Geode does.
Signed-off-by: Elliott Mitchell
Reviewed-by: Philip Prindeville 04/2023
---
target/linux/x86/config-5.15 | 5 +
target/linux/x86/config-6.1
Date: Tue, 31 Oct 2023 11:06:58 -0700
This is an internal boolean value. The value routinely gets
overriden and should never be overtly set.
Signed-off-by: Elliott Mitchell
---
target/linux/x86/64/config-5.15 | 1 -
target/linux/x86/64/config-6.1 | 1 -
target/linux/x86/generic
Date: Mon, 27 Feb 2023 17:24:27 -0800
These spots should be detecting the amd64 architecture, not the
specific target name. If additional amd64 targets were added, or
the target was renamed, these would fail to build.
Signed-off-by: Elliott Mitchell
---
package/firmware/intel-microcode
Date: Mon, 17 Apr 2023 08:21:26 -0700
All of the sublevels choose their own values, so there is no point
in the common file having anything. This also removes a warning from
the kernel build process.
Signed-off-by: Elliott Mitchell
Reviewed-by: Philip Prindeville 04/2023
---
target/linux/x86
Split the board.d files to isolate their data to associated
architectures. Seems wasteful to include all board-specific data
with every single build.
Signed-off-by: Elliott Mitchell
---
.../{ => 64}/base-files/etc/board.d/01_leds | 5 -
.../base-files/etc/board.d/02_network |
On Sat, Nov 25, 2023 at 07:08:20AM +0100, Felix Fietkau wrote:
> On 25.11.23 03:28, Elliott Mitchell wrote:
> >
> > All of these are plausible. I think modules selected in device
> > configurations should get built and installed into the root filesystem.
> > Otherw
On Tue, Jan 02, 2024 at 04:44:04PM -0800, Elliott Mitchell wrote:
> There is a desire to reduce the time spent on x86 OpenWRT platforms.
> "generic" is most suitable for removal. The few systems which could
> use "generic" must now opt for "legacy" (or fo
On Sat, Nov 25, 2023 at 07:08:20AM +0100, Felix Fietkau wrote:
> On 25.11.23 03:28, Elliott Mitchell wrote:
> > On Fri, Nov 24, 2023 at 01:53:01PM +0100, Jonas Gorski wrote:
> >> > > I'm fine with the cp -l change, but I think adding all remaining
> >> &
Handling common shell usage may have been valuable in the past. Yet now
this is almost unused, so inline the single remaining use. Then delete
the old file.
Signed-off-by: Elliott Mitchell
---
I've tried to test the removal. I'm unsure I actually achieved
coverage, so a careful look
The inconsistent calling had already been noticed. Now the trap
has been spotted, so clean this up.
Signed-off-by: Elliott Mitchell
---
scripts/kconfig.pl | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/scripts/kconfig.pl b/scripts/kconfig.pl
index 5a53e2154b
Match usual Perl style to make the operation of the script easier
to understand for future developers.
Signed-off-by: Elliott Mitchell
---
scripts/kconfig.pl | 27 ---
1 file changed, 8 insertions(+), 19 deletions(-)
diff --git a/scripts/kconfig.pl b/scripts/kconfig.pl
, this is what
spam has done to e-mail. It used to be rather faster and more reliable
than letters, yet now.
Elliott Mitchell (5):
scripts/kconfig.pl: fixup subroutine style
scripts/kconfig.pl: modify config_and()/config_sub() to match other
ops
scripts/kconfig.pl: switch to using
Having all operator-handling functions match the same prototype has
advantages.
Signed-off-by: Elliott Mitchell
---
scripts/kconfig.pl | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/scripts/kconfig.pl b/scripts/kconfig.pl
index f7b3814cdd..dd286479b3 100755
Ah, the wonders of pointers. Simplifies the configuration parsing
as all these cases are otherwise identical.
Signed-off-by: Elliott Mitchell
---
Oy vey. I only spotted passing the second arg to parse_expr() *just*
before I was initially planning to send this. That is quite the boody
trap
On Fri, Dec 08, 2023 at 11:14:38AM +0100, Robert Marko wrote:
> On Fri, 8 Dec 2023 at 11:13, Piotr Dymacz wrote:
> >
> > On 8.12.2023 11:02, Robert Marko wrote:
> > > On Fri, 8 Dec 2023 at 11:01, Piotr Dymacz wrote:
> > >>
> > >> Would it make sense to rename qualcommax to qualcomm and make
On Fri, Nov 24, 2023 at 01:53:01PM +0100, Jonas Gorski wrote:
>
> On Mon, 20 Nov 2023 at 02:37, Elliott Mitchell wrote:
> >
> > On Sat, Nov 18, 2023 at 07:57:35AM +0100, Felix Fietkau wrote:
> > > On 17.11.23 22:31, Elliott Mitchell wrote:
> > > > On Fri,
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,
On Wed, Nov 15, 2023 at 10:36:21AM +0100, Stefan Lippers-Hollmann wrote:
>
> On 2023-11-14, Elliott Mitchell wrote:
>
> > I don't know the future, but enabling kernel support is the first step.
>
> If you wanted to add it to Debian (with working a multi-arch
> implem
On Wed, Nov 15, 2023 at 11:29:23AM +0100, Bjørn Mork wrote:
> Elliott Mitchell writes:
>
> > Previously these would get built, then simply omitted from the
> > resultant image.
>
> A kernel image built with a config symbol set to 'm' is sometimes
> deliberately diff
On Sat, Nov 11, 2023 at 10:51:08PM -0800, Elliott Mitchell wrote:
> Modules built from kernel source will now be in $(LINUX_OBJ_DIR).
>
> Signed-off-by: Elliott Mitchell
> ---
> package/kernel/linux/modules/block.mk| 106 +++
> package/kernel/linux/modules/can
On Sat, Nov 18, 2023 at 07:57:35AM +0100, Felix Fietkau wrote:
> On 17.11.23 22:31, Elliott Mitchell wrote:
> > On Fri, Nov 17, 2023 at 05:20:33PM +0100, Felix Fietkau wrote:
> >> On 11.11.23 01:21, Elliott Mitchell wrote:
> >> > This removes the requirement for to cr
1 - 100 of 161 matches
Mail list logo
