From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3302#note_2024772394
Yes, It seems to be working fine on my machine as well. I didn't put it in the
initrd.
--
___
kernel mailing list -- k
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3302#note_2023354472
Do we know what happens on the x13s when both the kernel and userspace pd
mapper are enabled? (I'm testing it now.. but its building on device so will
take an hour
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3302#note_2023354472
Do we know what happens on the x13s when both the kernel and userspace pd
mapper are enabled?
--
___
kernel mailing list -- kernel
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3263#note_2008484611
The external contributor tag is presumably because you don't have a redhat.com
addr (or didn't sign in?) Also the commit message has a "Digutal" in it.
But otherw
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2926#note_1767163098
This looks sane to me too.
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le
From: Jeremy Linton
redhat/configs: For aarch64/RT, default kstack randomization off
Unlike other architectures which use their cycles counters to
seed the kstack randomization (which is sketchy) aarch64 uses
the kernel random number generator. For a list of reasons starting
with the lack of an
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2526#note_1442679421
Yes, I think this one leaked in and should probably be off as pbrobinson
mentions above because its dead code. There is a UEFI/ACPI RK3588 port
floating around, but given all the
From: Jeremy Linton
redhat/configs: Disable qcom armv7 drippings in the aarch64 tree
There are a few global clock controller (GCC), MMC, and phy modules
for some old armv7 qcom soc's still being statically built for the
aarch64 kernel. Lets disable them as AFAIK they aren't being use
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2154#note_1234624744
Presumably, a small selection of usb->wifi/etc and a couple rpi4 like devices
would suffice?
___
kernel mailing list -- ker
Hi,
On 12/8/22 06:58, Peter Robinson wrote:
On Thu, Dec 8, 2022 at 12:42 AM Adam Williamson
wrote:
Hi folks! Today I woke up and found
https://bugzilla.redhat.com/show_bug.cgi?id=2151495 , which diverted me
down a bit of an "installer environment size" rabbit hole.
As of today, with that ne
From: Jeremy Linton
[redhat] configs: Fix Layerscape regression
CONFIG_NXP now hides the NXP devices, which in the case
of the LX2k series is a tested fedora platform. Without
enabling CONFIG_NXP these platforms stop working because
the lack of CONFIG_LAYERSCAPE disables their drivers.
Cc
From: Jeremy Linton
redhat: configs: Disable FIE on arm
FIE intends to estimate cpu work for a given task more accurately.
On an ACPI/CPPC machine, the code can utilize PCC mailboxes
that trap to the firmware (which are all the CPPC machines
at this point). Meaning the CPU overhead of this
From: Jeremy Linton
[redhat] arm: turn SPE back on
While attempting to turn SPE on for all redhat distros
except for armv7 builds, the enable/disable was inverted
and it was left disabled for everything except for armv7.
This was incorrect, lets fix it.
Fixes: d76aee99af90 ("[redhat] arm:
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1393#note_781394705
INPUT_MATRIXKMAP gets triggered because of KEYBOARD_TEGRA which is selected
because CONFIG_ARCH_TEGRA is on. Those choices seem fairly reasonable IMHO if
TEGRA is enabled (which it is
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1393#note_777928842
No, I removed the ark override on CONFIG_KEYBOARD then moved the missing
definitions from fedora to common. Which makes them the same
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1529#note_777597493
See also https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1525
___
kernel mailing list -- kernel@lists.fedoraproject.org
To
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1393#note_777596635
which is similar but not identical to https://gitlab.com/cki-project/kernel-
ark/-/merge_requests/1525 I opened. The difference is that I'm honoring the
fedora config for the keyb
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1393#note_774807936
The merged config options don't appear to be complete, in my testing the at
keyboard is required by the hyperv_keyboard driver to actually enable the
keyboard. Hence why I opened
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1525#note_772087081
This MR is just the CONFIG_ changes for arm64/hyperv. There is another older
one which was originally just the CONFIG changes until I was able to test
them, and now includes a non
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1393#note_772080204
well just to confuse everyone, I pushed the entire patch set required to get
hyperv working here. That includes the config and the out of tree fix. So,
either this MR or the other one
From: Jeremy Linton
NOT_UPSTREAM/HYPERV: Enable HYPERV_TIMER on ARM64
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2007430
Upstream Status: RHEL-only
The existing windows/arm64 hyperv host expects that HYPERV_TIMER
is enabled by the linux guests (as x86), and so guests that
aren&#
From: Jeremy Linton on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1393
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2007430
Upstream Status: RHEL-only
Windows on Arm is a thing, and some of those machines support
HYPERV. For WoA users it would
From: Jeremy Linton
redhat/configs: Fixup HYPERV config on aarch64
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2007430
Upstream Status: RHEL-only
Windows on Arm is a thing, and some of those machines support
HYPERV. For WoA users it would be helpful if Fedora/etc
ran well as a guest
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1393#note_772033418
I should have pushed to this MR, but I opened another one
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1525 which fixes
the configs so that the hyperv_keyboard works. The
From: Jeremy Linton
redhat/configs: Fixup HYPERV config on aarch64
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2007430
Upstream Status: RHEL-only
Windows on Arm is a thing, and some of those machines support
HYPERV. For WoA users it would be helpful if Fedora/etc
ran well as a guest
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1440#note_713822249
I can't ack config options, otherwise, I would :kiss_mm:
So looks good to me!
___
kernel mailing list -- kernel@lists.fedoraproject.o
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1394#note_689579938
There is definitely a problem with the rodata checks, and for the moment the
console/disk don't actually seem to be working correctly, so i'm digging int
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1394#note_689519481
So, this look right and follows my other PR, but i'm curious what you're
testing it on. I upgraded a lenovo 5g to win11 and am now experiencing early
boot failures right befo
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1393#note_689518358
BTW: I haven't moved on this because I got my hands on a win11/lenovo 5g, and
am having a boot problem with it now. So, i'm still debu
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1393#note_686695272
Ok, I thought it was for rc's, my bad. I will move that (and the MTE bits).
___
kernel mailing list -- kernel@lists.fedoraproject.o
From: Jeremy Linton
redhat/configs: Enable HYPERV host support on aarch64
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2007430
Upstream Status: RHEL-only
Windows on Arm is a thing, and some of those machines support
HYPERV. For WoA users it would be helpful if Fedora/etc
ran well as a
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1333#note_674060479
Wierd this thing shows me a pile of unrelated commits because the rebase isn't
clean? Anway +1
___
kernel mailing list -- k
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1176#note_604459685
I will give this a late, thumbs-up-by :)
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/884#note_524524247
I've been meaning to re-post that with proper CC's and the like, but
have been off doing coresight stuff, which JCM just killed since marvell
isn't around asking
From: Jeremy Linton on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/884
Enable some arm options globally across ark & fedora. Some of these
options like coresight are already enabled in fedora and should be
enabled in ark, are enabled=y and should be =m
From: Jeremy Linton on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/884
Enable some arm options globally across ark & fedora. Some of these
options like coresight are already enabled in fedora and should be
enabled in ark, are enabled=y and should be =m
From: Jeremy Linton on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/884
Enable some arm options globally across ark & fedora. Some of these
options like coresight are already enabled in fedora and should be
enabled in ark, are enabled=y and should be =m
From: Jeremy Linton on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/884
Enable some arm options globally across ark & fedora. Some of these
options like coresight are already enabled in fedora and should be
enabled in ark, are enabled=y and should be =m
From: Jeremy Linton on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/785#note_462666414
Yes, it probably should at some point. I'm not sure if that is now or at
some point in the future, mostly because the centos test platform for
ark doesn't have o
Perf is capable of decoding coresite debug/trace files
but the feature needs to be enabled with CORESIGHT=1
and the decode library needs to be added as a build
dependency.
Signed-off-by: Jeremy Linton
---
kernel.spec | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a
Hi,
On 8/22/19 11:36 AM, Laura Abbott wrote:
On 8/22/19 8:58 AM, Prarit Bhargava wrote:
On 8/19/19 9:15 AM, Laura Abbott wrote:
On 8/16/19 2:57 PM, Paul Bolle wrote:
Florian Weimer schreef op vr 16-08-2019 om 14:04 [+0200]:
RHEL has a larger NR_CPU value, though. For example, it's 8192 on
x
The aarch64 kernel is a gzip'ed EFI image, this means
that pesign needs to sign the original image and then
zip it for grub to be able to validate the kernel image.
Signed-off-by: Jeremy Linton
---
kernel.spec | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
From: Jeremy Linton
The mmc/k3 driver is dependent on a number of other linux modules
which must be built into the initrd in order to use the mmc/sd
as a boot device for initrd/module based distros.
Normally this would be taken care of with linux's modules.deps
based on symbolic depende
Hi,
It seems that commit 8221dd34f turned off CONFIG_DRM_I2C_ADV7511. That
is the HDMI transmitter used on the 96boards hikey. The result is that
the framebuffer no longer works..
Can we get that config option enabled for just aarch64?
(I can submit a bug/patch/whatever if that is easier tha
Hi,
On 10/28/2016 03:29 PM, Jeremy Linton wrote:
The existing 42-bit VA used in fedora is quite limiting. Lets
turn on 48-bit VA's now that the core mozjs/polkit fixes are in
place.
In case it wasn't clear should have tagged this for rawhide/F26.. If
anyone would like to test it,
The existing 42-bit VA used in fedora is quite limiting. Lets
turn on 48-bit VA's now that the core mozjs/polkit fixes are in
place.
Signed-off-by: Jeremy Linton
---
config-arm64 | 3 +++
1 file changed, 3 insertions(+)
diff --git a/config-arm64 b/config-arm64
index 4156910..15027e3 1
On 05/13/2016 12:41 PM, Josh Boyer wrote:
On Thu, May 12, 2016 at 4:42 PM, Jeremy Linton wrote:
On 05/12/2016 02:59 PM, Peter Robinson wrote:
The ARM Juno development platform's PCIe is supported
by the generic PCI host driver. Enable it so that PCIe
attached peripherals work.
Push
On 05/12/2016 02:59 PM, Peter Robinson wrote:
The ARM Juno development platform's PCIe is supported
by the generic PCI host driver. Enable it so that PCIe
attached peripherals work.
Pushed as (F-24 and rawhide)
http://pkgs.fedoraproject.org/cgit/rpms/kernel.git/commit/?h=f24&id=decdd1f910500
On 05/12/2016 12:10 PM, Peter Robinson wrote:
On Thu, May 12, 2016 at 5:24 PM, Jeremy Linton wrote:
The ARM Juno development platform's PCIe is supported
by the generic PCI host driver. Enable it so that PCIe
attached peripherals work.
Pushed as (F-24 and rawhide)
The ARM Juno development platform's PCIe is supported
by the generic PCI host driver. Enable it so that PCIe
attached peripherals work.
Signed-off-by: Jeremy Linton
---
config-arm64 | 3 +++
1 file changed, 3 insertions(+)
diff --git a/config-arm64 b/config-arm64
index 77dde02..2db4e9a 1
50 matches
Mail list logo
