From: "Richard W.M. Jones" <rich@annexia.org>
To: SP <sp@orbitalfox.eu>
Cc: caml-list@inria.fr, "Nicolás Ojeda Bär" <nicolas.ojeda.bar@lexifi.com>
Subject: Re: [Caml-list] Status of the OCaml RISC-V port
Date: Sun, 25 Feb 2018 17:36:11 +0000 [thread overview]
Message-ID: <20180225173611.5ixubujcwmhkxrd3@annexia.org> (raw)
In-Reply-To: <20180225163008.ptcnxyzvx6flkz3n@darkstar>
On Sun, Feb 25, 2018 at 04:30:08PM +0000, SP wrote:
> On Sun, Feb 25, 2018 at 04:14:30PM +0000, Richard W.M. Jones wrote:
> > Fedora has been maintaining an out of tree RISC-V patch in our OCaml
> > package for about 18 months, from:
> >
> > https://github.com/nojb/riscv-ocaml/commits/trunk
>
> Is it possible to get with opam switch?
Do you mean on an x86_64 host? Given that I haven't finished
compiling all the deps for opam it definitely won't work in the Fedora
RISC-V image. In any case we're developing a distribution, so my
primary concern is with the Fedora OCaml package.
> > There are also development boards coming but it's likely you'll have
> > to wait til July for general availability and even then they will cost
> > $1000 and are not expected to have very good performance.
>
> I've been looking at this from the periphery, for 1k is a tall bill just
> for messing around. What's the forecast for something more affordable
> and usable?
Eventually, but not likely this year.
Rich.
next prev parent reply other threads:[~2018-02-25 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-25 16:14 Richard W.M. Jones
2018-02-25 16:30 ` SP
2018-02-25 17:36 ` Richard W.M. Jones [this message]
2018-02-25 19:29 ` David Allsopp
2018-02-25 21:35 ` SP
2018-02-25 22:35 ` Nicolás Ojeda Bär
2018-02-26 8:56 ` Xavier Leroy
2018-02-26 14:13 ` SP
2018-02-26 14:20 ` Richard W.M. Jones
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=20180225173611.5ixubujcwmhkxrd3@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=nicolas.ojeda.bar@lexifi.com \
--cc=sp@orbitalfox.eu \
/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).