From: JamiKettunen <JamiKettunen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pinephone-kernel: update to 6.1.3.
Date: Thu, 26 Jan 2023 20:08:08 +0100 [thread overview]
Message-ID: <20230126190808.oNX3iWD5ph8BqF7bd-PX-qxFxhbwl6jTIegttY82GG4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41654@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
New comment by JamiKettunen on void-packages repository
https://github.com/void-linux/void-packages/pull/41654#issuecomment-1405473558
Comment:
@jcgruenhage I know this isn't exactly the best place to write about this but if you don't mind could you check what configs Waydroid needs to work on the PinePhone? these should be mandatory for running the Android OS itself in LXC container, but extra things are most likely needed to setup the networking:
```
CONFIG_PSI=y
# CONFIG_PSI_DEFAULT_DISABLED is not set
CONFIG_ANDROID_BINDER_DEVICES=""
```
(the last one isn't mandatory but those default nodes aren't required since [`ANDROID_BINDERFS`](https://cateee.net/lkddb/web-lkddb/ANDROID_BINDERFS.html) is enabled for runtime binder configuration)
As a reference you can mostly just use `pmbootstrap kconfig check --waydroid --file <path to .config>` (maybe also check against `--container` if there's still issues)
next prev parent reply other threads:[~2023-01-26 19:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 19:34 [PR PATCH] " jcgruenhage
2023-01-15 14:56 ` sgn
2023-01-15 19:38 ` JamiKettunen
2023-01-15 19:39 ` JamiKettunen
2023-01-16 7:58 ` sgn
2023-01-21 20:47 ` [PR PATCH] [Updated] " jcgruenhage
2023-01-21 20:48 ` jcgruenhage
2023-01-21 21:11 ` jcgruenhage
2023-01-22 20:35 ` [PR PATCH] [Merged]: " Piraty
2023-01-26 19:08 ` JamiKettunen [this message]
2023-02-05 20:16 ` Piraty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230126190808.oNX3iWD5ph8BqF7bd-PX-qxFxhbwl6jTIegttY82GG4@z \
--to=jamikettunen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).