Package Base Details: linux-mainline

Git Clone URL: (read-only)
Submitter: miffe
Maintainer: miffe
Last Packager: miffe
Votes: 227
Popularity: 0.559052
First Submitted: 2011-07-22 06:50
Last Updated: 2019-06-24 13:31

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

kgizdov commented on 2017-04-13 11:04

@WozMzy, sorry, I misunderstood how the config was handled. I thought it was just taken plainly from core, who has already applied olddefconfig. That is fine then.

WorMzy commented on 2017-04-12 23:32

@kgizdov: As miffe said, the core package's config is used as a base and is updated with olddefconfig which sets all new config options to their recommended/default values.

If you are unhappy with the upstream defaults, complain there. Alternatively, roll your own config as Det suggested.

kgizdov commented on 2017-04-12 22:10

@miffe, as I said, regardless of the flag I mentioned, you are saying you are using a config from a different version of Linux. That is not how Linux works. This is a problem. You can run the built-in conf routine in the Linux source yourself and then diff against the one from another version. You will find that they have huge differences. Please try to mitigate this.

miffe commented on 2017-04-10 11:38

@kgizdov: The core config is updated with make olddefconfig before building. It hasn't caused a problem yet. And core can add that flag when they update to 4.11 and then i'll merge it back here.

Det commented on 2017-04-10 09:55

I don't suppose it matters either too much, since it's just a module, but also on that, isn't it easy enough to just enable nconfig to go through your own changes?

kgizdov commented on 2017-04-10 09:49

@miffe, a lot of the times you need a different config with newer versions of the kernel. How do you justify using the "old" config from the core package? I don't necessarily mean you to add my flag in particular, but core cannot and will not add it because it doesn't exist for linux 4.10, but it does for linux 4.11. It's bad practice not to update the config to match the version of linux.

basica commented on 2017-04-10 08:59

@miffe, thanks. I will wait till it becomes a stable kernel, and if not included in the default config log a request with the arch devs.

miffe commented on 2017-04-10 08:50

@basica, kgizdov: This package uses the same config as core/linux, i wont to diverge from that. But once it's added there it will be here aswell.

basica commented on 2017-04-10 08:28

I was/am the maintainer for linux-ct which was the linux kernel patched to add support for HDMI sound for cherry/bay trail CPUs. This is now in the mainline kernel, but support isn't built by the default config. I don't suppose the config could be modified so that CONFIG_HDMI_LPE_AUDIO=m is added by default?


kgizdov commented on 2017-04-07 17:17

Has anyone tried building with PCIEASPM_POWER_SUPERSAVE or PCIEASPM_POWER_SAVE. I wonder if we should add it to the config. Thoughts? (