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

On Fri, Jan 30, 2004 at 08:25:40PM +0100, Egbert Eich wrote:
> Sven Luther writes:
>  > 
>  > 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.
>  > 
> 
> Yes, a personal agreement between driver developers would also work.
> However they tend to change and other people will make contributions
> who all would have to agree also. 
> I don't know if a general dual license agreement in the kernel 
> file header would be possible. Also it could get removed once 
> the author changes. Just like the license in the XFree86 driver 
> could be amended. 

I guess already some drivers have such a dual licencing.

> Doing this now for existing fbdev driver would involve to ask
> anyone who has contributed little more than a typo fix.

Yeah, that would be rather problematic, but anyway, most of the things
move from the XFree86 code to fbdev code, and most often, it is not code
that is copied, but the register information and such. It is always
easier to get specs if you are working for XFree86 than if you plan to
do some kernel driver work.

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 22:29 UTC|newest]

Thread overview: 15+ 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     ` [forum] Re: Announcement: Modification to the base XFree86(TM) license Sven Luther
2004-01-30 19:25       ` Egbert Eich
2004-01-30 22:29         ` Sven Luther [this message]
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
     [not found] <20040131113753.GA19133@iliana>
2004-01-31 13:06 ` Andrew C Aitchison
2004-01-31 22:24   ` Benjamin Herrenschmidt
2004-02-01 22:33   ` Ryan Underwood
2004-02-02 11:41   ` Sven Luther
2004-02-02 13:13     ` Harold L Hunt II
2004-02-02 16:04       ` Sven Luther
2004-02-02 13:59     ` Dr Andrew C Aitchison

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=20040130222902.GA11885@iliana \
    --to=sven.luther@wanadoo.fr \
    --cc=devel@XFree86.Org \
    --cc=eich@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).