From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 365] ROCM/Libre-SOC GPU Opcode interoperability
Date: Sun, 07 Jun 2020 02:50:16 +0000
Message-ID: <bug-365-13-B6LotvGsRA@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-365-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=365
Cole Poirier <colepoirier@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |colepoirier@gmail.com
--- Comment #2 from Cole Poirier <colepoirier@gmail.com> ---
I watched this LinuxConf talk that I think is salient you this discussion,
sometime in the last year and rewatched it today. But Mummy I don't want to use
CUDA - Open source GPU compute, https://m.youtube.com/watch?v=ZTq8wKnVUZ8. It
seems like Dave Aerlie at Red Hat Melbourne would be someone worth talking to
about this.
Not quite as related thoughts:
In the future perhaps the standardization of an open compute stack could be
undertaken by the OpenPower Foundation. Just spitballing here, I have no idea
of practicality or feasibility.
A related (OPF Linux conf) thing with this talk about booting faster
(https://m.youtube.com/watch?v=fTLsS_QZ8us) reminded me of our discussion of
using our single core iteration as a first stage boot processor, but I’m
posting it here as it’s so what related, and I could find the boot stage
processor discussion searching bugzilla. I’d like to migrate this to the
Systèmes Librés Bugzilla once we have that discussion and set up what we decide
on.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 23:57 [libre-riscv-dev] [Bug 365] New: " bugzilla-daemon
2020-06-06 23:58 ` [libre-riscv-dev] [Bug 365] " bugzilla-daemon
2020-06-07 2:50 ` bugzilla-daemon [this message]
2020-06-07 3:03 ` bugzilla-daemon
2020-06-07 3:31 ` bugzilla-daemon
2020-06-07 3:47 ` bugzilla-daemon
2020-06-07 4:30 ` bugzilla-daemon
2020-06-07 17:41 ` bugzilla-daemon
2020-06-07 17:52 ` bugzilla-daemon
2020-06-07 20:21 ` bugzilla-daemon
2020-06-07 20:29 ` bugzilla-daemon
2020-06-07 21:23 ` bugzilla-daemon
2020-06-07 21:39 ` bugzilla-daemon
2020-06-09 17:04 ` bugzilla-daemon
2020-06-12 18:24 ` bugzilla-daemon
2020-06-12 21:40 ` Luke Kenneth Casson Leighton
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=bug-365-13-B6LotvGsRA@https.bugs.libre-soc.org/ \
--to=bugzilla-daemon@libre-soc.org \
--cc=libre-riscv-dev@lists.libre-riscv.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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git