all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: phodina <phodina@protonmail.com>
Cc: Science Fiction <forevercomputerr@gmail.com>, help-guix@gnu.org
Subject: Re: PinePhone Pro & Guix
Date: Thu, 29 Dec 2022 02:45:06 +0100	[thread overview]
Message-ID: <20221229024506.13155961@primary_laptop> (raw)
In-Reply-To: <5VSz0QgnBEuKtOXNNyXRS_nfEDol_ingxMzrVqi1i_5Br3Fw6LbiTSLEOc9Lb55gMSbVH-3YDu5ttGQSAD55NwyqDG4_C9Hy3vZNbUrD6EM=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 2622 bytes --]

On Sat, 24 Dec 2022 20:18:30 +0000
phodina <phodina@protonmail.com> wrote:

> Hello,
Hi,

> > Hi all, I'm trying to write a guix code that will generate images
> > for pinephone pro. Can anyone share the config .scm file if anyone
> > has done it? Thanks.  
> 
> I do have same interest in mind. The bigger issue I'd say is to have
> working mobile UI environment as the console would otherwise be
> useless.
> 
> There are two possibilites:
> - Plasma mobile [1][2]
> - Phosh [3][4]
If people buy the keyboard addon it's also possible to use additional
environments like sxmo that was mentioned before (an environment that
works 100% with a keyboard).

> After these environments are running in Guix we can look into the
> hardware. The biggest drawback I'd say is that's still development
> platform.
Users probably just need to be aware of it[1].

> Sure you can use it daily but the mileage varies from
> Android or iOS (mainly power and peripherals such as camera)[6].
> Though the work already done is amazing and continues to improve!
> 
> Besides the code not yet being merged in the upstream kernel there's
> another issue.
That would be an issue indeed. Though if packages are added, it might
be possible to easily support the Pinephone (the not-pro version) or
other smartphones with upstream kernels.

> FIY I've been putting together the definition for the Pine64 products
> on nonguix channel :-)
With a little amount of work, it might be possible to use Pine64 devices
supported by upstream Linux and u-boot. And as I understand, there is
not a lot of packaging to do for the Pinephone, so it might also
benefit other phones, or at least show how to do it in a way that works.

Though having everything packaged will not magically adapt
all the applications to a very small screen with a very high resolution
for instance, or magically port free software Android applications to
GNU/Linux. Some Android applications will also not work with Waydroid
if they require hardware features that Waydroid doesn't support yet
(like telephony for the "silence" application).

Another issue might be that not everything cross compile fine in Guix,
and cross compiling from x86_64 is needed so to have downloadable images
like for the Pinebook PRO[2].

Though things could be done in two stages where once the image is
installed, the users would then just use guix system reconfigure to
install additional packages.

References:
-----------
[1]https://wiki.pine64.org/index.php/PinePhone#Thermal_safety
[2]https://guix.gnu.org/en/download/latest/

Denis.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2022-12-29  1:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22 10:22 PinePhone Pro & Guix Science Fiction
2022-12-24 20:18 ` phodina
2022-12-24 21:30   ` david larsson
2022-12-24 23:21     ` Vagrant Cascadian
2022-12-24 23:35   ` Vagrant Cascadian
2022-12-29  1:45   ` Denis 'GNUtoo' Carikli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-29  4:51 Help-Guix Digest, Vol 85, Issue 50 jgart
     [not found] ` <mailman.16844.1672287760.1249.help-guix@gnu.org>
2022-12-29  5:02   ` PinePhone Pro & Guix jgart

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=20221229024506.13155961@primary_laptop \
    --to=gnutoo@cyberdimension.org \
    --cc=forevercomputerr@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=phodina@protonmail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.