Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 288] intro post for powerpc-notebook.org and https://www.powerprogress.org/en/
Date: Wed, 22 Apr 2020 16:00:39 +0000
Message-ID: <bug-288-13-8tmyMacMx9@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-288-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=288

--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Yehowshua from comment #3)
> Ah I see. That makes sense to me.
> 
> So this:
> 
> LibreSOC is an Open Hardware and Open Software project that aims to deliver
> a physical  POWER compliant SOC that comes complete with a CPU, GPU, VPU,
> and DDR controller. All the software and hardware from the drivers down to
> the RTL and VLSI cells are open. 

libre-licensed.  "open" leaves the possibility of accusations of "fake open
source".

"we'll release the code when it's revision 1.0... but it's open!".

"we'll release the code when it's ready... but it's open!"

"we'll release the code... under a non-commercial license... but it's open!"

> LibreSOC is also providing the necessary
> drivers amongst which include Vulkan and OpenCL drivers.

no, not OpenCL.  that has to come later as we'll need an entire new
grant to do it.

> The intended market includes customers who desire acceleration in the
> embedded space without relying on ARM's proprietary drivers that have been
> know to break in the past.

and piss people off :)

> The first iteration of LibreSOC targets a single-core at 180nm. Subsequent
> generations target more cores at a smaller node size.

looks good.  i'd put "target multiple SMP cores" though.  "more cores"
could mean "NUMA" or "SIMT".  SIMT is almost impossible to program for
general-purpose, and NUMA is a royal pain, memory-wise.

-- 
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

  parent reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19 19:29 [libre-riscv-dev] [Bug 288] New: " bugzilla-daemon
2020-04-22 12:26 ` [libre-riscv-dev] [Bug 288] " bugzilla-daemon
2020-04-22 12:49 ` bugzilla-daemon
2020-04-22 15:41 ` bugzilla-daemon
2020-04-22 16:00 ` bugzilla-daemon [this message]
2020-04-22 16:16 ` bugzilla-daemon
2020-04-22 19:00 ` bugzilla-daemon
2020-04-22 19:14 ` bugzilla-daemon
2020-04-22 19:42 ` bugzilla-daemon

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-288-13-8tmyMacMx9@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