Masanori Ogino authored 7 months ago and Clayton Craft committed 7 months ago

This change adds patches for fixing `make menuconfig` failures with old
kernels due to changes in GNU Make and C compilers.

Signed-off-by: Masanori Ogino <mogino@acm.org>
[ci:skip-build]: already built successfully in CI

Part of https://gitlab.com/postmarketOS/pmaports/-/issues/2401

[ci:skip-build]: already built successfully in CI

Part of https://gitlab.com/postmarketOS/pmaports/-/issues/2401

[ci:skip-build]: already built successfully in CI

Newbyte authored 11 months ago and Newbyte committed 11 months ago

Part of https://gitlab.com/postmarketOS/pmaports/-/issues/2401

[ci:skip-build]: already built successfully in CI

socksinspace authored 1 year ago and Newbyte committed 1 year ago

This fixes building for linux-lg-vee7e, and adds a shared patch.

The shared patch replaces the "Solaris style flags" in piggy.gzip.S

[ci:skip-build]: already built successfully in CI

mulingLHY authored 1 year ago and Newbyte committed 1 year ago

[ci:skip-build]: Already built successfully in CI.

Henrik Grimler authored 1 year ago and Oliver Smith committed 1 year ago

linux3.4-ARM-8933-1-replace-Sun-Solaris-style-flag-on-section-xz-supplementation.patch
contains an addition that was not part of
linux3.4-ARM-8933-1-replace-Sun-Solaris-style-flag-on-section.patch
simply because error did not occur with the config I tested with.

[ci:skip-build]: already built successfully in CI

Karl Chan authored 1 year ago and Clayton Craft committed 1 year ago

[ci:skip-build]: Already built successfully in CI.

Henrik Grimler authored 1 year ago and Oliver Smith committed 1 year ago

With recent gcc versions we get errors like:

/linux/arch/arm/mm/proc-v7.S: Assembler messages:
/linux/arch/arm/mm/proc-v7.S:425: Error: junk at end of line, first unrecognized character is `#'

Seen on at least two samsung kernels based on 3.4 and 3.10. Fix issue
by backporting (part of) commit found in mainline.

blacksilver authored 1 year ago and Pablo Correa Gomez committed 1 year ago

[ci:skip-build]: already built successfully in CI

Przemysław Romanik authored 2 years ago and Oliver Smith committed 1 year ago

[ci:skip-build]: already built successfully in CI

Shinjo Park authored 2 years ago and Oliver Smith committed 2 years ago

Merge and move Spreadtrum patches from these kernels to shared-patches:
* linux-finepower-f1
* linux-samsung-{gtel3g,gtelwifi,j1mini3g,j3xnlte}
* linux-zte-p731a20

[ci:skip-build]: already built successfully in CI

Minecrell authored 4 years ago and Alexey Minnekhanov committed 4 years ago

These are various debugging related patches that I have used over the time
when attempting to get new features working for the mainline kernel.
Given that the downstream kernel is just intended for debugging in this case,
it seems convenient to add them to pmaports so I don't need to go search for
them in case I need them again in the future.

[ci:skip-build] Already built on CI

Luca Weiss authored 4 years ago and Bart Ribbers committed 4 years ago

[ci:skip-build]
[ci:ignore-count]
[ci:skip-vercheck]

Luca Weiss authored 4 years ago and Oliver Smith committed 4 years ago

Mostly the GCC10 yylloc failure was seen but several others have been
observed:

* wireguard script was silently failing
* several gcc10 x86 errors
* a checksum from kernel.org has changed

Now we have 3 different gcc10 yylloc patches:

gcc10-extern_YYLOC_global_declaration.patch:
    Linux < 4.2

linux4.2-gcc10-extern_YYLOC_global_declaration.patch:
    Linux 4.2+

linux4.17-gcc10-extern_YYLOC_global_declaration.patch:
    Linux 4.17+

[ci:skip-build]
[ci:ignore-count]
[ci:skip-vercheck]

Dzmitry authored 4 years ago and Bart Ribbers committed 4 years ago

Patch makes yyloc declaration extern.

Minecrell authored 5 years ago and Alexey Minnekhanov committed 5 years ago

All the downstream kernels reference ../../.shared-patches in their
symlinks. Now that we have moved device ports to device/testing/*,
those symlinks are no longer working.

Changing the path would require fixing all downstream packages *and*
a new pmbootstrap release. Overall it seems easier to move the
.shared-patches folder to device/.shared-patches.

Since it is only relevant for downstream kernel packages in device/
that might be a better place in general.