-
Notifications
You must be signed in to change notification settings - Fork 248
linux-qcom-next/linux-yocto-dev: enable more use cases #1180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
koenkooi
wants to merge
10
commits into
qualcomm-linux:master
Choose a base branch
from
koenkooi:koen/qcom-next-zram
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+190
−0
Draft
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
e22b4e1
linux-qcom-next: enable ZRAM
koenkooi 2f897b8
linux-qcom-next: enable in-kernel wifi features for iwd
koenkooi a9bb2ce
linux-qcom-next: enable BINFMT_MISC to prevent podman crash
koenkooi ce3d549
linux-qcom-next: enable all LED triggers
koenkooi 8604530
linux-qcom-next: enable namespaces
koenkooi 5fee75d
linux-yocto-dev: enable ZRAM
koenkooi f4286f6
linux-yocto-dev: enable in-kernel wifi features needed for iwd
koenkooi 8f067ff
linux-yocto-dev: enable namespace support
koenkooi 7b63a36
linux-yocto-dev: set ZRAM options to =m
koenkooi 6b65be7
linux-qcom-next: set ZRAM options to =m
koenkooi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think most of these should be built as modules already. Could you please check / confirm?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll check later today, this section of the config is a copy/paste of what iwd told me to enable. I can turn all tristate options in
=m, but I'd like to keep this list of options to make it easier to lift it into different kernels, that won't have anything enabled yet.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd rather not keep the full list here. It is ridiculously long and verbose. Most of the options are enabled by default. If you list all of them, for me it means that all of them are set incorrectly in the qcom-next config or in the defconfig.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The options that are enabled in linux-qcom-next in its current form are these:
Which means that this specific kernel only needs the following:
I'd still like to keep the complete list, since that makes it easier and less error-prone to copy this between kernels (linux-qcom-next, linux-yocto-dev, linux-yocto and vendor kernels).
I also don't trust upstream linux to not regress defconfigs, especially for things we currently don't test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you want a comprehensive list, please also enable ARM-specific crypto acceleration options.
At the same time, enabling obsolete & broken algorithms (DES, MD4, MD5) sounds very strange to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
EAP-PEAP with MsCHAPv2 still uses MD4, EAP-MD5 uses, well MD5 and 3DES is sadly still allowed as an alternative to AES when using 802.1x :(
I'll have a look at the ARM-specific crypto options.