9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] 9front on the Allwinner A64
Date: Mon, 28 Nov 2022 08:56:44 +0100 (GMT+01:00)	[thread overview]
Message-ID: <0df780bc-37c8-4f01-8c40-aa50e83d0573@sirjofri.de> (raw)
In-Reply-To: <CAPfmpJC4Nh_cPvb0y5HpUs7sZx=yuSs1tSTr1UBBw98J9j+8nQ@mail.gmail.com>


28.11.2022 01:27:59 adventures in9 <adventuresin9@gmail.com>:

> Looks like I have some extra reading to do tonight.
> The Pine64 folks were kind enough to post the datasheet for the A64
> https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf

Yes, and they also have the schematics for their boards you'll definitely find useful. I skimmed through the A64 manual (and obviously skipped the irrelevant pages for now), it's big, but well structured.

Btw there's also a lowlevel community specifically for pine devs on their discord (which is also available through matrix and maybe even irc, idk). There's a handful of nice and helpful people there. They also would be happy about a Plan 9 on pinephone, though they probably wouldn't know what to do with it.

My long-term goal is to create a basis for a full Plan 9 phone, that means, building a few basic touch-friendly apps, like a launcher and stuff like that. It will really be a challenge since I want to try capturing the Plan 9 concepts there, for example, it should be easily possible to plumb things, snarf-and-paste, and I'd like to develop a touch-friendly text interface. Obviously there's a long way until I can really run software like that on the pinephone, but due to compatibility I should be able to develop those apps fully on an amd64, run with mouse, and it should work on a pinephone automatically (after recompile).

sirjofri


  reply	other threads:[~2022-11-28  7:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-27 19:45 sirjofri
2022-11-28  0:26 ` adventures in9
2022-11-28  7:56   ` sirjofri [this message]
2022-11-28 21:06     ` adventures in9
2022-11-28 21:20       ` unobe
2022-11-28 22:44       ` Kurt H Maier
2022-11-29  8:04         ` sirjofri
2022-11-29 14:42           ` Kurt H Maier
2022-11-29 16:50             ` sirjofri
2022-11-29 18:04               ` Tom Schwindl
2022-11-29 18:59                 ` adventures in9
2022-11-29 19:23                   ` Tom Schwindl
2022-11-30  2:38           ` Stuart Morrow
2022-11-30  6:34             ` adventures in9
2022-12-01 14:12               ` Stuart Morrow
2022-11-30  2:35       ` Stuart Morrow

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=0df780bc-37c8-4f01-8c40-aa50e83d0573@sirjofri.de \
    --to=sirjofri+ml-9front@sirjofri.de \
    --cc=9front@9front.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).