linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: forum@xfree86.org
Cc: devel@XFree86.Org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [forum] Re: Announcement: Modification to the base XFree86(TM) license.
Date: Fri, 30 Jan 2004 18:32:38 +0100	[thread overview]
Message-ID: <20040130173238.GA8599@iliana> (raw)
In-Reply-To: <16410.33783.236964.200047@xf11.fra.suse.de>

On Fri, Jan 30, 2004 at 05:19:03PM +0100, Egbert Eich wrote:
> Benjamin Herrenschmidt writes:
> 
>  > 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.
> 
> Relating to that: exchanging code between XFree86 and kernel has been a
> one-way road so far. The GPL the kernel is under doesn't allow us to
> port back improvements that have been made to the kernel to our drivers
> Even though this isn't covered by the GPL the author of the driver 
> or the changes could still give the permission to do so.
> 
> I whish there was a better exchange between kernel fbdev developers
> and driver developers here.

Maybe a decision on both parts on this would be ok ? XFree86 could make
sure the licence of the driver code would not conflict with the GPL,
keeping the old one for example, and the fbdev driver authors would
dual-licence the code, both GPL and the old xfree86 licence would do
just fine. Benjamin, what do you think about this ?

BTW, CCing this to the linux-fbdev mailing list.

Friendly,

Sven Luther


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

       reply	other threads:[~2004-01-30 17:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040129115838.A70069@xfree86.org>
     [not found] ` <1075423804.12536.28.camel@gaston>
     [not found]   ` <16410.33783.236964.200047@xf11.fra.suse.de>
2004-01-30 17:32     ` Sven Luther [this message]
2004-01-30 19:25       ` [forum] Re: Announcement: Modification to the base XFree86(TM) license Egbert Eich
2004-01-30 22:29         ` Sven Luther
2004-01-31  9:10           ` Andrew C Aitchison
2004-01-31 11:37             ` Sven Luther
2004-01-31 22:07             ` Ryan Underwood
2004-01-31 21:48           ` Mark Vojkovich
2004-01-31 12:27         ` Thomas Winischhofer

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=20040130173238.GA8599@iliana \
    --to=sven.luther@wanadoo.fr \
    --cc=devel@XFree86.Org \
    --cc=forum@xfree86.org \
    --cc=linux-fbdev-devel@lists.sourceforge.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).