Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Hendrik Boom <hendrik@topoi.pooq.com>
To: libre-riscv-dev@lists.libre-riscv.org
Subject: Re: [libre-riscv-dev] Clarifying the difference between Kazan and Mesa 3D Vulkan
Date: Thu, 12 Mar 2020 09:53:53 -0400
Message-ID: <20200312135353.jt2lgatbvjmcd53s@topoi.pooq.com> (raw)
In-Reply-To: <20200217000021.GB1920@localhost>

On Mon, Feb 17, 2020 at 05:30:26AM +0530, Veera wrote:
> On Sun, Feb 16, 2020 at 12:12:48PM -0800, Cole Poirier wrote:
> > Hi all, but I think particularly Jacob and Luke. I’m having trouble figuring out the different roles that Kazan and Mesa 3d Vulkan are going to play in the 3Dgpu. I’m sure this will be obvious in hindsight but could you help me understand the purpose of each and the differences between the two? (Or point me to the relevant mailing list thread, I’ve tried looking here: http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-January/003302.html, but I’m still having difficulty).
> > 
> 
> OpenGL as a 3D Graphics API had origin in SGI Graphics. Which was closed source.
> Mesa was the first open source software based OpenGL implementation.
> 
> Vulkan is the new Graphics API released by Khronos.
> Currently Vulkan is implemented in Mesa for hardware drivers only.
> And Kazan is first software based Vulkan implementation for Mesa meaning
> a vulkan program runs entirely in CPU using kazan.
> 
> If I know correctly, libre-riscv will support Vulkan using kazan.

Makes sense, because our graphics *will* run in (a) CPU(s).
And is there a Mesa that takes Opengl commands and calls Vulcan?

-- hendrik

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

       reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7FE7A78D-3C2E-4A29-893A-FDEBA4389E6E@gmail.com>
     [not found] ` <20200217000021.GB1920@localhost>
2020-03-12 13:53   ` Hendrik Boom [this message]
2020-03-12 14:10     ` 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=20200312135353.jt2lgatbvjmcd53s@topoi.pooq.com \
    --to=hendrik@topoi.pooq.com \
    --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