From: Andrew Nazarov <andrew.nazarov.intres@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 3D graphics as a filesystem
Date: Thu, 13 Oct 2016 08:38:10 +0300 [thread overview]
Message-ID: <CAMQYav-vQzJsJScqHhk-AQMZBkVkd_JbN23Z+-GX14YFkK+a_A@mail.gmail.com> (raw)
In-Reply-To: <B32FCAAD-3707-4094-ACED-D701958EF291@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]
Chris, if you find something interesting, please share the knowledge. A few
days ago I asked to myself the same question, but Google didn't help me
much.
On 13 October 2016 at 02:47, Chris McGee <newton688@gmail.com> wrote:
> Cool. Do you have any code that you can share for that? What does the file
> protocol look like?
>
> On Oct 12, 2016, at 7:17 PM, Jules Merit <jules.merit.eurocorp.us@
> gmail.com> wrote:
>
> 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: 2248 bytes --]
prev parent reply other threads:[~2016-10-13 5:38 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
2016-10-12 23:47 ` Chris McGee
2016-10-13 5:38 ` Andrew Nazarov [this message]
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=CAMQYav-vQzJsJScqHhk-AQMZBkVkd_JbN23Z+-GX14YFkK+a_A@mail.gmail.com \
--to=andrew.nazarov.intres@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).