9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jules Merit <jules.merit.eurocorp.us@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 3D graphics as a filesystem
Date: Wed, 12 Oct 2016 16:17:37 -0700	[thread overview]
Message-ID: <CAEVxPTPaf7Uu2ecsUPMtCcOqiW0foKivCJm6iiJjKbcV8xu0+Q@mail.gmail.com> (raw)
In-Reply-To: <5067D49A-FA55-4746-9151-7DD8A25167BE@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]

Yeah I prototyped draw3d with 9vx driver to host GPU on Linux system.
MesajGL if 9p file exists it supports mode of that name to transfer to gpu.
It helps if you have DooM handy to try writing it in rc.

On Oct 12, 2016 4:06 PM, "Chris McGee" <newton688@gmail.com> wrote:

> Hello All,
>
> I am looking at the specs for a GPU and was thinking about something
> analogous to /dev/draw, but for 3D graphics. Kind of like OpenGL except
> exposed as a filesystem so that it is network mountable and programmed in
> any language (even rc).
>
> Does anyone know if this kind of thing has been done before for plan 9?
> Any relevant papers or documents out there?
>
> My first thought involves representing elements in the graphics pipeline
> as files where you can write shader language code. Also a vertex file to
> write or read floating point vertex data. Maybe something more abstract
> would be better with scene graph and camera controls would be better match
> for a filesystem implementation.
>
> Thanks,
> Chris
>

[-- Attachment #2: Type: text/html, Size: 1312 bytes --]

  parent reply	other threads:[~2016-10-12 23:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 23:03 Chris McGee
2016-10-12 23:12 ` James A. Robinson
2016-10-12 23:21   ` Stanley Lieber
2016-10-12 23:17 ` Jules Merit [this message]
2016-10-12 23:47   ` Chris McGee
2016-10-13  5:38     ` Andrew Nazarov

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=CAEVxPTPaf7Uu2ecsUPMtCcOqiW0foKivCJm6iiJjKbcV8xu0+Q@mail.gmail.com \
    --to=jules.merit.eurocorp.us@gmail.com \
    --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).