9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] A sad story and a question
Date: Sat, 10 Nov 2007 15:28:21 -0800	[thread overview]
Message-ID: <E5491081-5E04-4C34-A9E9-939B218E1DD8@telus.net> (raw)
In-Reply-To: <20071110192411.C93835B50@mail.bitblocks.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>
> I suspect a lot of eyecandy would be easier to implement on
> plan9.  I have been thinking about openGL on plan9.  Has
> anyone looked at adding openGL to Plan9?

Disclaimer: I work for Intel, in a graphics group tied closely to  
GPUs.  All my words are mine, as are my opinions, and don't represent  
Intel.

There is no deep technical reason not to add OpenGL to plan9.  It is,  
however, one hell of a big effort if you want hardware acceleration,  
not easily undertaken by hobbyists.  Each hardware device to support  
requires substantial driver work and compiler work - shader compilers  
must be targeted to particular GPUs these days.

If I were going the route of enabling 3D graphics on Plan9 I'd  
probably flat out ditch the OpenGL model.  Instead I'd probably treat  
the GPU as a remote machine, and use 9P to provide namespace in which  
you could bind textures, vertex buffers, frame buffers, shaders, and  
so on.  A control channel would be used to launch tasks using these  
named resources.  There's minor issues involving virtualization in  
the absence of sufficient resources, but I'm hoping the days of small  
graphics cards will be behind us long before I can get around to  
coding such a driver...

Paul

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHNj6VpJeHo/Fbu1wRAlNDAJwIQkQ2ySgUak8gqciLKHplZV88LQCfYUAf
Kq1ZGLllXlN5fADssVJdKAc=
=mtgh
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2007-11-10 23:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-10  2:13 Pietro Gagliardi
2007-11-10  2:49 ` geoff
2007-11-10  3:00   ` Pietro Gagliardi
2007-11-10  4:50     ` ron minnich
2007-11-10  4:55       ` Pietro Gagliardi
2007-11-10 13:04         ` erik quanstrom
2007-11-10 17:31         ` ron minnich
2007-11-10 18:58           ` David Leimbach
2007-11-10 19:00             ` Pietro Gagliardi
2007-11-10 23:48               ` David Leimbach
2007-11-12  3:19                 ` Russ Cox
2007-11-10 19:24             ` Bakul Shah
2007-11-10 19:46               ` andrey mirtchovski
2007-11-10 21:20                 ` john
2007-11-10 23:28               ` Paul Lalonde [this message]
2007-11-11  0:27                 ` Anthony Sorace
2007-11-11  1:12                   ` Paul Lalonde
2007-11-11  1:12                 ` Joel C. Salomon
2007-11-11  5:34                   ` Paul Lalonde
2007-11-12 20:32                 ` 3d graphics (was " Bakul Shah

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=E5491081-5E04-4C34-A9E9-939B218E1DD8@telus.net \
    --to=plalonde@telus.net \
    --cc=9fans@cse.psu.edu \
    /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).