9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Lawrence E. Bakst" <ml@iridescent.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Cute plan9/inferno client?
Date: Thu, 27 Jan 2011 23:57:26 -0500	[thread overview]
Message-ID: <p06240816c967e571b63d@[192.168.1.155]> (raw)
In-Reply-To: <2c95dd590ea0f02d58b3e10c2b3d7b54@ladd.quanstro.net>

A few comments.

1. It was a 1 line post to the group. I'm not pushing anything, have no vested interest, I just wanted the list to be aware of it. You don't like Nvida or closed source, that's fine with me. The Tegra is probably one of the best ARM chips out there and certainly the most integrated given the graphics and video hardware it has.

I'll point that companies like TI, that used to hate open source are now converts. Many of the Gumstix Overo modules that seem to be so beloved here, have PowerVR SGX chips on them that are 100% closed source.

2. All previous (to Sandy Bridge) Intel graphics hardware is pretty much junk. It's not very DX capable or OpenGL capable as far as 3D goes. The chips are riddled with bugs. They can't play even simple games and the performance is awful. Last time I checked the 3D portion of the hardware did not seem to be open source and documented, although that might have changed.

3. I don't believe any of the major 3D chips vendors has a fully open source driver That include Nvidia, ATI, S3, and Imagination Technologies. Where fully open source would mean that the compiler and other tools for their shader units, thread dispatchers, and so on is all open source. Or the code that reads the
EDID via DDI/I2c from the monitor.

Actually these chips will never be fully open source because of licensing constraints for things like HDCP and Blu-ray.

leb


At 1:16 PM -0500 1/27/11, erik quanstrom wrote:
> > I deleted a line from the post that said the big issue will be the
>> quality of the hardware doc, if there even is any.  Still, if it ends
>> up running linux there might be some hope.
>
>the problem is that the linux driver guy is generally getting it straight
>from the source, and not from the docs.  so (from experience)
>existence of a linux driver does not imply that there are docs,
>or if there are, a new driver could be written from them.
>
>> I wouldn't rule out getting doc on everything but the 3D unit.  Even
>> in that case, some of Nvidia's 3D GPUs instruction sets have been
>> reverse engineered.
>
>if you have time for that kind of nonsense, go ahead.  there
>are full specs on the intel video hardware, and nobody has
>done a think with that.
>
>> In case you haven't noticed all of the major 3D chips guys are closed
>> source.
>
>ati?
>
>- erik


--
leb@iridescent.org




  parent reply	other threads:[~2011-01-28  4:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27 17:35 Lawrence E. Bakst
2011-01-27 17:38 ` erik quanstrom
2011-01-27 18:00   ` Lawrence E. Bakst
2011-01-27 18:16     ` erik quanstrom
2011-01-28  2:45       ` hiro
2011-01-28  2:47         ` erik quanstrom
2011-01-28  3:04         ` Skip Tavakkolian
2011-01-28  4:57       ` Lawrence E. Bakst [this message]
     [not found]       ` <p06240816c967e571b63d@192.168.1.155>
2011-01-28 21:31         ` Venkatesh Srinivas
2011-01-28 21:56           ` erik quanstrom
2011-01-28 23:42             ` hiro
2011-01-29 10:40             ` Venkatesh Srinivas
2011-01-29 10:51           ` Lawrence E. Bakst
     [not found]           ` <p0624080bc969982a9965@192.168.1.155>
2011-01-29 11:09             ` Venkatesh Srinivas
2011-01-29 13:17               ` erik quanstrom
2011-01-29 23:56               ` Noah Evans
2011-01-28 10:06     ` Richard Miller
2011-01-28 12:50       ` hiro
2011-01-28 13:36         ` erik quanstrom
2011-02-01 16:56           ` Ethan Grammatikidis
2011-02-01 22:27             ` hiro
2011-02-01 22:52               ` erik quanstrom
2011-01-27 18:01   ` Lawrence E. Bakst

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='p06240816c967e571b63d@[192.168.1.155]' \
    --to=ml@iridescent.org \
    --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).