All of lore.kernel.org
 help / color / mirror / Atom feed
From: Howard Chu <hyc@symas.com>
To: Piotr Gluszenia Slawinski <curious@bwv190.internetdsl.tpnet.pl>
Cc: Dave Airlie <airlied@redhat.com>,
	Timothy Meade <zt.tmzt@gmail.com>,
	linux-arm-msm@vger.kernel.org,
	Saravana Kannan <skannan@codeaurora.org>,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: Closed source userspace graphics drivers with an open source kernel component
Date: Thu, 01 Jul 2010 21:54:08 -0700	[thread overview]
Message-ID: <4C2D70F0.7090100@symas.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1007020456250.9535@bwv190.internetdsl.tpnet.pl>

Piotr Gluszenia Slawinski wrote:
>> There is no point supporting companies that give you a little bit of
>> information in exchange they want the support that being in a mainline
>> kernel gives. Its an unfair exchange of knowledge and time, and if they
>> claim they have to make a profit then its even more unfair.
>
> also, they seem to do it quite wrong way. i.e. much simpler would be to
> just implement regular, open driver , and implement additional crypto
> mechanism in chipset itself, allowing to use simple userspace program
> sending certified keys allowing GPU to operate.
> if key is not available and device/driver not paid/registered, then
> GPU would simply lock itself , similiar to pre-paid designs from
> company whose name should not be spoken aloud.
>
> also certain functionality could be ordered with same chip structure,
> i.e. framebuffer, unaccelerated 2d, accel 2d, 3d, etc.
> with user buying proper 'entry level' pre-paid code set from manufacturer.
>
> this would provide quite same functionality (profit), without impacting
> open-source projects like Xorg with unnessesary complications.

Pardon me for intruding in this discussion, but I'm astonished that you 
actually find what you posted to be acceptable. If I pay for a piece of 
hardware, I have the right to use it. Requiring certified keys before it 
performs the function for which it was purchased is pure nonsense.

-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/

WARNING: multiple messages have this Message-ID (diff)
From: Howard Chu <hyc@symas.com>
To: Piotr Gluszenia Slawinski <curious@bwv190.internetdsl.tpnet.pl>
Cc: Dave Airlie <airlied@redhat.com>,
	Timothy Meade <zt.tmzt@gmail.com>,
	linux-arm-msm@vger.kernel.org,
	Saravana Kannan <skannan@codeaurora.org>,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: Closed source userspace graphics drivers with an open source kernel component
Date: Thu, 01 Jul 2010 21:54:08 -0700	[thread overview]
Message-ID: <4C2D70F0.7090100@symas.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1007020456250.9535@bwv190.internetdsl.tpnet.pl>

Piotr Gluszenia Slawinski wrote:
>> There is no point supporting companies that give you a little bit of
>> information in exchange they want the support that being in a mainline
>> kernel gives. Its an unfair exchange of knowledge and time, and if they
>> claim they have to make a profit then its even more unfair.
>
> also, they seem to do it quite wrong way. i.e. much simpler would be to
> just implement regular, open driver , and implement additional crypto
> mechanism in chipset itself, allowing to use simple userspace program
> sending certified keys allowing GPU to operate.
> if key is not available and device/driver not paid/registered, then
> GPU would simply lock itself , similiar to pre-paid designs from
> company whose name should not be spoken aloud.
>
> also certain functionality could be ordered with same chip structure,
> i.e. framebuffer, unaccelerated 2d, accel 2d, 3d, etc.
> with user buying proper 'entry level' pre-paid code set from manufacturer.
>
> this would provide quite same functionality (profit), without impacting
> open-source projects like Xorg with unnessesary complications.

Pardon me for intruding in this discussion, but I'm astonished that you 
actually find what you posted to be acceptable. If I pay for a piece of 
hardware, I have the right to use it. Requiring certified keys before it 
performs the function for which it was purchased is pure nonsense.

-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/

  reply	other threads:[~2010-07-02  5:21 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01 22:10 Closed source userspace graphics drivers with an open source kernel component Dave Airlie
2010-07-01 22:10 ` Dave Airlie
2010-07-01 22:36 ` Dave Airlie
2010-07-01 22:36   ` Dave Airlie
2010-07-01 22:51   ` Daniel Walker
2010-07-01 22:51     ` Daniel Walker
2010-07-01 22:57     ` Dave Airlie
2010-07-01 22:57       ` Dave Airlie
2010-07-01 23:29       ` Daniel Walker
2010-07-01 23:29         ` Daniel Walker
2010-07-01 23:37         ` Dave Airlie
2010-07-01 23:37           ` Dave Airlie
2010-07-01 23:37           ` Dave Airlie
2010-07-02  0:08           ` Daniel Walker
2010-07-02  0:08             ` Daniel Walker
2010-07-02  0:08             ` Daniel Walker
2010-07-02  0:13             ` Dave Airlie
2010-07-02  0:13               ` Dave Airlie
2010-07-02  0:18               ` Saravana Kannan
     [not found]                 ` <AANLkTilsqmCZwLUNJhvDKkralHQZzlRV3ZxaIGbt9-xB@mail.gmail.com>
2010-07-02  0:38                   ` Timothy Meade
2010-07-02  0:42                     ` Timothy Meade
2010-07-02  0:42                       ` Timothy Meade
2010-07-02  2:46                       ` Dave Airlie
2010-07-02  2:46                         ` Dave Airlie
2010-07-02  2:46                         ` Dave Airlie
2010-07-02  3:01                         ` Piotr Gluszenia Slawinski
2010-07-02  3:01                           ` Piotr Gluszenia Slawinski
2010-07-02  3:01                           ` Piotr Gluszenia Slawinski
2010-07-02  4:54                           ` Howard Chu [this message]
2010-07-02  4:54                             ` Howard Chu
2010-07-02  6:52                             ` Piotr Gluszenia Slawinski
2010-07-02  6:52                               ` Piotr Gluszenia Slawinski
2010-07-02  6:52                               ` Piotr Gluszenia Slawinski
2010-07-14 13:24                           ` Pavel Machek
2010-07-16  0:42                             ` Tim HRM
2010-07-16  0:42                               ` Tim HRM
2010-07-01 23:51 ` Piotr Gluszenia Slawinski
2010-07-02  1:27   ` Corbin Simpson
2010-07-02  1:27     ` Corbin Simpson
2010-07-02  7:48 ` Christoph Hellwig
2010-07-02  9:58 ` Luc Verhaegen
2010-07-02 10:15   ` Christoph Hellwig
2010-07-02 11:12     ` Luc Verhaegen
2010-07-02 11:26       ` Dave Airlie
2010-07-02 11:26         ` Dave Airlie
2010-07-02 10:23   ` Dave Airlie
2010-07-02 10:23     ` Dave Airlie
2010-07-02 11:10     ` Luc Verhaegen
2010-07-02 11:53       ` Dave Airlie
2010-07-02 11:53         ` Dave Airlie
2010-07-02 12:07         ` "C. Bergström"
2010-07-02 12:07           ` "C. Bergström"
2010-07-02 14:45           ` Xavier Bestel
2010-07-02 15:03             ` "C. Bergström"
2010-07-04  7:06         ` Magnus Wendt
2010-07-04  7:27           ` Dave Airlie
2010-07-04  7:27             ` Dave Airlie
2010-07-04 11:03             ` Theodore Tso
2010-07-04 15:37               ` Matthew Garrett
2010-07-04 15:37                 ` Matthew Garrett
2010-07-04 20:05               ` Dave Airlie
2010-07-04 20:05                 ` Dave Airlie
2010-07-02 14:01       ` Anton Vorontsov
2010-07-03  0:41   ` Ian Romanick
2010-07-03  0:41     ` Ian Romanick
2010-07-03 11:46   ` Garry Hurley

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=4C2D70F0.7090100@symas.com \
    --to=hyc@symas.com \
    --cc=airlied@redhat.com \
    --cc=curious@bwv190.internetdsl.tpnet.pl \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skannan@codeaurora.org \
    --cc=zt.tmzt@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.