[Deepin Kernel SIG] [Debian] Apply some changes to better support package build system #545
Conversation
We want to enable use of the Android ashmem and binder drivers to support Anbox, but they should not be built-in as that would waste resources and increase security attack surface on systems that don't need them. - Add a MODULE_LICENSE declaration to ashmem - Change the Makefiles to build each driver as an object with the "_linux" suffix (which is what Anbox expects) - Change config symbol types to tristate Update: In upstream commit 721412e titled "staging: remove ashmem" the ashmem driver was removed entirely. Secondary commit message: "The mainline replacement for ashmem is memfd, so remove the legacy code from drivers/staging/" Consequently, the ashmem part of this patch has been removed.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
| * ABS.fmt/NEG.fmt execution mode. | ||
| */ | ||
| static enum { STRICT, EMULATED, LEGACY, STD2008, RELAXED } ieee754 = STRICT; | ||
| enum ieee754_mode { STRICT, EMULATED, LEGACY, STD2008, RELAXED }; |
There was a problem hiding this comment.
不清楚这里需要选择 RELAXED 还是 EMULATED
和EMULATED没关系，只是从STRICT改为RELAXED吧。
解释说明如下：
`The IEEE Std 754 compliance mode requested is determined by the main executable. Any dynamic shared objects loaded in addition shall respect the mode according to the rules set below.
For strict' executables all the dynamic shared objects shall follow the same legacy-NaN or 2008-NaN ABI, as denoted by the EF_MIPS_NAN2008 flag described in Section 3.1. The value of the flag shall be the same across the executable and all the dynamic shared objects loaded together. Both strict' and legacy' dynamic shared objects shall be accepted, however relaxed' ones shall be rejected regardless of the value of their EF_MIPS_NAN2008 flag.
For relaxed' executables any dynamic shared objects shall be accepted, strict', relaxed' and legacy' alike, regardless of the value of their EF_MIPS_NAN2008 flag.
For legacy' executables the compliance mode is determined by the value of bit #25 in the a_val' member of the AT_FLAGS entry of the auxiliary vector received from the kernel. The value of 0' shall make the dynamic loader follow the rules for strict' executables. The value of 1' shall make the dynamic loader follow the rules for relaxed' executables.`
We want to enable use of the Android binder driver to support Waydroid, but it should not be built-in as that would waste resources and increase security attack surface on systems that don't need it. Export the currently un-exported symbols it depends on. Signed-off-by: Ben Hutchings <ben@decadent.org.uk> Signed-off-by: WangYuli <wangyuli@uniontech.com>
There are 2 mode of value of IEEE NaN hardcoded by CPU. Currently, our mipsel/mips64el port is in so-called lagacy mode. Loongson 3A 4000 is set as the so-called 2008 mode. To make Debian workable on Loongson 3A 4000, we need set the kerenl in RELAXED mode. https://web.archive.org/web/20180830093617/https://dmz-portal.mips.com/wiki/MIPS_ABI_-_NaN_Interlinking [bwh: Update for addition of EMULATED mode in 6.11]
We want to include the Debian version in the utsname::version string instead of a full timestamp string. However, we still need to provide a standard timestamp string for gen_initramfs_list.sh to make the kernel image reproducible. Make mkcompile_h use $KBUILD_BUILD_VERSION_TIMESTAMP in preference to $KBUILD_BUILD_TIMESTAMP.
For distribution binary packages we assume $DISTRIBUTION_OFFICIAL_BUILD, $DISTRIBUTOR and $DISTRIBUTION_VERSION are set. Signed-off-by: Ben Hutchings <ben@decadent.org.uk> Signed-off-by: WangYuli <wangyuli@uniontech.com>
|
测试通过 |
Avenger-285714
merged commit d2c044f
into
deepin-community:linux-6.6.y
deepin pr auto review代码审查意见：
|
Avenger-285714
changed the title
6 participants
Those each patch needs to be evaluated before merging, some may require trimming or modification.
The decision to merge a patch should be based on its merits.
Origin patches list:
Link: https://salsa.debian.org/kernel-team/linux/-/tree/debian/latest/debian/patches?ref_type=heads