Your message dated Tue, 21 Mar 2023 14:16:29 +0100
with message-id <2222739.xpBMn53rMx@prancing-pony>
and subject line Re: Bug#1033176: linux: Future Android/Waydroid support
has caused the Debian Bug report #1033176,
regarding linux: Future Android/Waydroid support
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1033176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: Future Android/Waydroid support
Severity: wishlist
Forwarded: https://github.com/waydroid/waydroid/issues/811
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
In https://salsa.debian.org/kernel-team/linux/-/merge_requests/651 I had
initially removed the 2 Android related patches for the following
reason:
Drop patches:
- debian/android-enable-building-ashmem-and-binder-as-modules.patch
- debian/export-symbols-needed-by-android-drivers.patch
After https://bugs.debian.org/901492 the preceding 2 patches were
created for anbox support. However in kernel 5.18 `ashmem` was removed
from the upstream kernel and since then, anbox has not been working as
reported in https://bugs.debian.org/1014329.
Then in https://bugs.debian.org/1032304, titled "RM: anbox -- ROM;
Upstream discontinued", the anbox package has been removed from the
Debian archive. And on Anbox's GH page one can see the following:
"It's development has however stalled in the past years and it's only
fair to say that now in 2023 it's no longer actively developed."
So it's of no use to continue carrying these patches.
Even though anbox is removed from the Debian archive and upstream more
or less 'dead', it turns out that Waydroid (= ~ anbox's successor) could
probably benefit from support in the Debian kernel too.
So I undid/reverted the dropping of those patches.
Removal of Android support should be done separately and ideally based on
a bug report in the BTS, hence this bug report.
In https://github.com/waydroid/waydroid/issues/811 I asked 'upstream'
for recommendations on which/how/what kernel modules to enable.
- -- System Information:
Debian Release: 12.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500,
'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-6-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-----BEGIN PGP SIGNATURE-----
iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCZBZPHwAKCRDXblvOeH7b
bpbCAPsFqbmYhJzizpispzGdw+ksgNnm59ZQDtmSMSYcNk5S5gD9FcHWbGx6XtJ2
5YefJ1PVNv1BbtdAkofzw2Nz5gLLDgE=
=pyYQ
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Sunday, 19 March 2023 00:54:15 CET Diederik de Haas wrote:
> In https://github.com/waydroid/waydroid/issues/811 I asked 'upstream'
> for recommendations on which/how/what kernel modules to enable.
In https://git.kernel.org/linus/9e18d0c82f0c07f2a41898d4adbb698a953403ee the
default value of BINDER_DEVICES was changed to "binder,hwbinder,vndbinder"
whereas the Debian kernel only has "binder". Also in other places they use the
3 values, but I haven't been able to find out *why*.
As I wouldn't be able to make the argument to change it to something else and
the most important thing is to enable ANDROID_BINDER_IPC, which is already the
case, there's no need to keep this bug open.
If someone *can* substantiate why and how things should be changed, they
should file a bug report (themselves) making the case.
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
