From: Conor Williams <conor.williams@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] GSoC 2021 project ideas
Date: Mon, 20 Sep 2021 08:37:42 +0000 [thread overview]
Message-ID: <CAL6pNZ-+2H0PL9xGUcD2fEmA1_xRU6u5+5g218ycnv3zfak9gQ@mail.gmail.com> (raw)
In-Reply-To: <CAFSF3XPJB0O71HxrThhzouQMPedAZW+GjaXQ0US2+E9yKBxQMg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3596 bytes --]
some of the fuseblk disc/k drivers/modules on peppermint which is a flavour
of ubuntu
are not even in the kernel space and there are mount.XYZ processes left
open which are
wide open to attack (with # fuser -p <PID>) /c09
for those chips tings
On Mon, Sep 20, 2021 at 8:24 AM hiro <23hiro@gmail.com> wrote:
> i think the main reason people are willing to fall for the android
> platform is bec. there is no good long-term supply of updated phone
> hardware with backwards-compatible interfaces.
>
> a lot of qualcomm and mediatek chipsets are being built, but instead
> of documentation they only ship half-baked linux drivers, which are
> often not even mainlined.
>
> those linux drivers are already hard to make work on actual linux
> distributions, or even on android distributions.
>
> who wants to reverse-engineer the hardware over and over again based
> on such linux drivers...
>
> On 9/20/21, Ethan Gardener <eekee57@fastmail.fm> wrote:
> > tl;dr: forget inferno, port plan 9 to the pine phone.
> >
> > On Mon, Sep 20, 2021, at 6:43 AM, Dave Eckhardt wrote:
> >> > Anyone know if this project went anywhere?
> >> >
> >> > https://www.cs.cmu.edu/~412/lectures/L05_Purge_Proposal.pdf
> >
> > I had to laugh at one of the slides. Inferno running natively on "x86
> > supercomputer"? I think implementing multicore support would be a first
> > step, not to mention 64-bit! While it would be nice if those jobs were
> done,
> > they will take time and effort. Overall, if porting natively, I see
> little
> > sense in preferring Inferno to Plan 9, especially as Plan 9 already
> supports
> > 64-bit multicore.
> >
> >> Sadly, not. One issue is that modern Android releases don't
> >> support 32-bit executables, and at the time that project was
> >> attempted Inferno was somewhat 32-bit (I haven't looked since).
> >
> > Recalling the issues Hellaphone had and the time it took, I'm of the
> opinion
> > that getting Inferno to work on any given phone's Linux kernel is hardly
> > more worthwhile than porting it directly to the hardware. The kernels
> have
> > undocumented interfaces.
> >
> > A current thread on OSdev (operating system development) forums is
> looking
> > at phones. It's a little rambly, but it reports on some encouraging
> things.
> > Lots of "baseband processors" (the phone-network communication
> subsystems)
> > have documented interfaces. There are at least 2 phones available now
> which
> > are fully open for operating system development: the PinePhone and the
> > Librem 5. (5 is the screen size.) Of the 2, the Pine Phone seems better,
> not
> > least because it can boot from the SD card; useful for testing.
> > https://forum.osdev.org/viewtopic.php?f=1&t=53251
> >
> > There's also the option of building your own phone out of components. The
> > thread has some info. I'm guessing most here would prefer a PinePhone.
> >
> >> But I think I saw some recent-ish Inferno-on-Android activity here:
> >>
> >> https://github.com/bhgv/Inferno-OS-bhgv
> >
> > That's probably a good source of code. bhgv is a freelance programmer who
> > was very interested in Inferno and made several improvements including
> > Truetype fonts. The last I heard was he tried to find paid work involving
> > Inferno but couldn't, so he didn't have time to work on it.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T39aec8f3f9d8503d-Md3c9ddc97c8acc196f3b1896
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 5638 bytes --]
next prev parent reply other threads:[~2021-09-20 8:38 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 19:23 [9fans] Plan 9 Applying to GSoC 2021 Anthony Sorace
2021-02-01 0:31 ` ~vidak
2021-02-01 9:35 ` sirjofri
2021-02-01 11:07 ` svaderaa
2021-02-01 11:26 ` Bakul Shah
2021-02-02 1:15 ` raingloom
2021-02-01 7:16 ` [9fans] GSoC 2021 project ideas (WAS: Re: Plan 9 Applying to GSoC 2021) cigar562hfsp952fans
2021-02-01 20:46 ` Steve Simon
2021-02-03 14:14 ` Ethan Gardener
2021-02-01 21:47 ` [9fans] GSoC 2021 project ideas sirjofri
2021-02-03 14:07 ` Ethan Gardener
2021-08-06 16:25 ` Jack Johnson
2021-08-19 21:06 ` unobe
2021-09-20 4:52 ` [9fans] " cigar562hfsp952fans
2021-09-20 5:08 ` Conor Williams
2021-09-20 5:11 ` vidak
2021-09-20 15:02 ` ori
2021-09-20 5:43 ` [9fans] " Dave Eckhardt
2021-09-20 7:51 ` Ethan Gardener
2021-09-20 8:23 ` hiro
2021-09-20 8:37 ` Conor Williams [this message]
2021-09-20 8:39 ` Conor Williams
2021-09-20 8:45 ` Conor Williams
2021-09-20 8:52 ` Conor Williams
2021-09-20 8:58 ` Conor Williams
2021-09-20 11:06 ` Conor Williams
2021-09-21 9:01 ` Ethan Gardener
2021-09-20 11:05 ` sirjofri
2021-09-20 11:08 ` Conor Williams
2021-09-20 14:01 ` sirjofri
2021-09-21 9:25 ` Ethan Gardener
2021-02-02 8:29 ` [9fans] GSoC 2021 project ideas (WAS: Re: Plan 9 Applying to GSoC 2021) tlaronde
2021-02-03 15:07 ` Ethan Gardener
2021-01-19 11:08 ` pouya+lists.9fans
2021-02-03 18:58 ` Ethan Gardener
2021-02-06 2:17 ` David Arroyo
2021-02-03 18:26 ` ori
2021-02-03 23:31 ` Skip Tavakkolian
2021-02-05 16:42 ` Ethan Gardener
2021-02-07 22:59 ` [9fans] Re: GSoC 2021 project ideas cigar562hfsp952fans
2021-02-09 0:26 ` Steve Simon
2021-02-09 1:59 ` [9fans] " Jeff Sickel
2021-02-09 0:34 ` [9fans] " Ethan Gardener
2021-02-02 5:30 ` [9fans] Plan 9 Applying to GSoC 2021 ori
2021-02-02 10:40 ` [9fans] Project idea (was: Plan 9 Applying to GSoC 2021) sirjofri
2021-02-02 16:07 ` [9fans] Re: Plan 9 Applying to GSoC 2021 Jeff Sickel
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=CAL6pNZ-+2H0PL9xGUcD2fEmA1_xRU6u5+5g218ycnv3zfak9gQ@mail.gmail.com \
--to=conor.williams@gmail.com \
--cc=9fans@9fans.net \
/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).