ALT Linux kernel packages development
 help / color / mirror / Atom feed
From: Anton Farygin <rider@altlinux.com>
To: devel-kernel@altlinux.ru
Subject: [d-kernel] [dawes@XFree86.Org: Re: Announcement: Modification to the base XFree86(TM) license.]
Date: Sat, 31 Jan 2004 19:40:24 +0300
Message-ID: <20040131164024.GI30388@master.altlinux.ru> (raw)

FYI.

----- Forwarded message from David Dawes <dawes@XFree86.Org> -----

Date: Fri, 30 Jan 2004 12:42:44 -0500
From: David Dawes <dawes@XFree86.Org>
To: devel@xfree86.org
Cc: forum@xfree86.org
Subject: Re: Announcement: Modification to the base XFree86(TM) license.
X-Original-To: rider@altlinux.com
Delivered-To: rider@localhost.altlinux.ru
User-Agent: Mutt/1.2.5i
In-Reply-To: <1075423804.12536.28.camel@gaston>; from benh@kernel.crashing.org on Fri, Jan 30, 2004 at 11:50:40AM +1100
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on public.xfree86.org
X-Spam-Status: No, hits=0.0 required=6.0 tests=none autolearn=no version=2.63
X-Spam-Level: 
Reply-To: devel@xfree86.org

On Fri, Jan 30, 2004 at 11:50:40AM +1100, Benjamin Herrenschmidt wrote:
>On Fri, 2004-01-30 at 03:58, David Dawes wrote:
>> Announcement: Modification to the base XFree86(TM) license.
>> 
>> After a thorough re-examination of the XFree86(TM) license and reviewing
>> how it fits in with the Project's long-stated licensing philosophy ("You
>> can do what you like with the code except claim that you wrote it."),
>> The XFree86 Project, Inc. has made some changes to its base license.
>> This license review was prompted by a desire to ensure that XFree86 and
>> its contributors are receiving due credit for their work.  The text of
>> the modified license can be found at
>> <http://www.xfree86.org/legal/licenses.html>.
>>
>> .../...
>
>Hi David !
>
>I'm no license/legal expert, but do that mean the licence becomes GPL
>incompatible ? In that case, that basically means you are screwing up
>any effort to make a decent graphics driver model in the linux kernel.
>
>If I'm wrong on that, you can skip the rest of this email.
>
>We rely heavily on the XFree drivers as those are updated & maintained
>by the card vendors or people working for them ("nv" by Mark Vojkovich,
>"radeon" by Hui Yu).
>
>Losing the ability of porting code straight from these to the fbdev
>drivers will basically kill all my efforts to turn the kernel radeonfb
>into a decent driver as I need to be able to re-use the code ATI puts
>in the XFree version. I suppose the same will happen to linux rivafb.
>
>So right when we are considering a new & saner video driver model for
>Linux, you are doing this move which screws up by blocking us from our
>primary source of information & support from the gfx card vendors.

Ben,

On looking through the fbdev drivers in the Linux kernel source, I see
very few cases where license notices from XFree86 driver source are
included.  This means that either the license for these drivers has no
impact on the work you are talking about (making what you have written
above moot), or some authors of portions of the current Linux fbdev code
have violated the terms of the existing licenses by not including a
verbatim copy of the copyright, license notice, and disclaimer text in
relevant source code.

I would also like to echo Egbert's comments about the one-way nature of
your concerns.

David
-- 
David Dawes
developer/release engineer                      The XFree86 Project
www.XFree86.org/~dawes
_______________________________________________
Devel mailing list
Devel@XFree86.Org
http://XFree86.Org/mailman/listinfo/devel

----- End forwarded message -----


             reply	other threads:[~2004-01-31 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-31 16:40 Anton Farygin [this message]
2004-01-31 21:03 ` [d-kernel] " Alexey Tourbin
2004-02-01  9:01   ` Anton Farygin
2004-02-01  9:41     ` Michael Shigorin
2004-02-01 10:02       ` Anton Farygin

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=20040131164024.GI30388@master.altlinux.ru \
    --to=rider@altlinux.com \
    --cc=devel-kernel@altlinux.ru \
    /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

ALT Linux kernel packages development

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel-kernel/0 devel-kernel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel-kernel devel-kernel/ http://lore.altlinux.org/devel-kernel \
		devel-kernel@altlinux.org devel-kernel@altlinux.ru devel-kernel@altlinux.com
	public-inbox-index devel-kernel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel-kernel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git