+ devel@xxxxxxxxxxxxxxxxxxxxxx
resending to Greg KH as instructed by his mail bot
I a few words the question is:
Has CONFIG_ANDROID_BINDER_IPC_32BIT been removed
in 1190b4e38f97023154e6b3bef61b251aa5f970d0 ("ANDROID: binder: remove
32-bit binder interface")
for a mandatory reason (incompatibilty with Android P build) or for
other reason and
the option could have been left (to be disabled in P builds)?
Also as android-x86 team contributor I'd like to understand what would
happen with P
if besides binder ipc 64bit the concurrent binder ipc 32bit had be
kept present and enabled.
Thanks
Mauro Rossi
2018-06-16 11:44 GMT+02:00 Mauro Rossi <issor.oruam@xxxxxxxxx>:
> Hi Martijn,
>
> I wanted to check with you what is the real reason for disabling it,
> because In my understanding in Android P you could have
> build 32bit Android image by disabling it, with this setting in the 32bit
> *_defconfig:
>
> # CONFIG_ANDROID_BINDER_IPC_32BIT is not set
>
> (which is ok if 64 binder is enabled in BoardConfig.mk, e.g oreo-x86 branch
> of android-x86)
>
> Are you sure there are no other users of kernel 4.18 for nougat derived
> builds or android-* fellow projects?
>
> It's no problem for me to partially revert
> 1190b4e38f97023154e6b3bef61b251aa5f970d0
> to keep the m68k improvement,
>
> but is this change due to "Android P need to use the 64-bit binder
> interface"
> (which is not mandatory, given the flexibility to disable it in *_defconfig)
> or just "we want to avoid people doing the mistake to enable it on P"?
>
> Mauro Rossi
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
