9front - general discussion about 9front
 help / color / mirror / Atom feed
From: adventures in9 <adventuresin9@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] 9front on the Allwinner A64
Date: Sun, 27 Nov 2022 16:26:17 -0800	[thread overview]
Message-ID: <CAPfmpJC4Nh_cPvb0y5HpUs7sZx=yuSs1tSTr1UBBw98J9j+8nQ@mail.gmail.com> (raw)
In-Reply-To: <51022878-2dcf-42be-9990-60f2d1475ce5@sirjofri.de>

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

On Sun, Nov 27, 2022 at 11:49 AM sirjofri
<sirjofri+ml-9front@sirjofri.de> wrote:
>
> Hello,
>
> adventuresin9 recently mentioned the A64 in the last video[1]. There are quite a few people interested in getting a 9front system on A64 powered devices (e.g. the pinephone).
>
> Here's my attempt at porting 9front to that platform[2]. It's in the early stages and only a few things work.
>
> To be precise, I can only boot the program (I wouldn't call it "kernel" yet) using uboot and output stuff to the serial console. I tried setting up a proper memory map, but when activating it I can't get the mapped hardware addresses for the serial connection working.
>
> The linked source directory is meant to be placed as a full directory to /sys/src/9/a64. Feel free to use that as a starter (or not as it really is not much).
>
> For me, I can try to help as much as I can. I own a pinephone and can test things, but I probably can't help much with lowlevel stuff (although I'd love to). I have to learn most things and I don't have much time to focus on learning it.
>
> If you want to reach me off-list, my mail address is the same, but without the plus stuff, so just sirjofri@....
>
> sirjofri
>
>
> [1] https://youtu.be/WG4zIu9KLPA
> [2] http://sirjofri.de/a64/

  reply	other threads:[~2022-11-28  0:28 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 [this message]
2022-11-28  7:56   ` sirjofri
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='CAPfmpJC4Nh_cPvb0y5HpUs7sZx=yuSs1tSTr1UBBw98J9j+8nQ@mail.gmail.com' \
    --to=adventuresin9@gmail.com \
    --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).