From: "Aram Hăvărneanu" <aram.h@mgk.ro>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 port to Raspberry Pi 3 Model B (ARM64)?
Date: Tue, 1 Mar 2016 12:04:46 +0100 [thread overview]
Message-ID: <CAEAzY3_w4_CGvDWafuJ1Gnahk7WZZEGkSifEHamNMD3R-_3tcQ@mail.gmail.com> (raw)
In-Reply-To: <CAK-yzPPqitEBeuMe6DV+ShGHMdDz2Ec8Z8Tx5TDochFpWpguBQ@mail.gmail.com>
On Tue, Mar 1, 2016 at 11:04 AM, Mark Lee Smith <netytan@gmail.com> wrote:
> What about NetBSD drivers?
What about them? NetBSD doesn't support the Pi3. What drivers do
we want anyway?
> As I understand it the Rump project provides a clean way to run
> NetBSD drivers in different environments. I guess the bigger problem
> here is be getting them past the compiler?
It is unfeasible to use the Plan 9 toolchain for this. Not only is
the C dialect different, and the assembly dialect completely
different, but the code expects a certain calling convention provided
by gcc and different from the Plan 9 calling convention.
Doing a rump port with gcc, cross-compiling on Unix and running on
Plan 9, should be easy though.
--
Aram Hăvărneanu
next prev parent reply other threads:[~2016-03-01 11:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 20:06 Skip Tavakkolian
2016-02-29 20:28 ` Richard Miller
2016-02-29 20:33 ` Bakul Shah
2016-02-29 21:46 ` erik quanstrom
2016-03-01 10:04 ` Mark Lee Smith
2016-03-01 11:04 ` Aram Hăvărneanu [this message]
2016-03-03 14:50 ` Richard Miller
2016-03-03 15:28 ` Charles Forsyth
2016-03-03 15:31 ` Charles Forsyth
2016-03-03 15:37 ` Richard Miller
2016-03-03 16:14 ` Charles Forsyth
2016-09-07 23:54 ` James A. Robinson
2016-03-02 6:49 ` Ramakrishnan Muthukrishnan
2016-03-02 9:10 ` Richard Miller
2016-03-02 9:22 ` Ramakrishnan Muthukrishnan
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=CAEAzY3_w4_CGvDWafuJ1Gnahk7WZZEGkSifEHamNMD3R-_3tcQ@mail.gmail.com \
--to=aram.h@mgk.ro \
--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).