linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Verhaegen <libv@skynet.be>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH 06/20] vt8623fb: New framebuffer	driver for VIA VT8623
Date: Sun, 6 May 2007 04:07:42 +0200	[thread overview]
Message-ID: <20070506020742.GA19784@skynet.be> (raw)
In-Reply-To: <20070506013617.GA29760@sci.fi>

On Sun, May 06, 2007 at 04:36:17AM +0300, Ville Syrjälä wrote:
> 
> I think a big portion of the blame falls on VIA since they are the
> original authors and the they have decided not to work with the community.
> Maybe that's changing now that they posted the patches (even though they
> aren't clean). I didn't really read the viafb patch thread so I missed the
> details. Are they are prepared to clean it up or do they just expect to
> dump the code here and forget about it?

I of course don't know anything what i say here for sure, but i'd be 
really surprised if VIA did change their act.

VIA has a history of either:
* freeing code, seeing it cleaned up and included in the relevant 
project, yet continuing a seperate fork in VIA-space nonetheless (X 
driver).
* purposefully forking projects to keep VIA specific adaptations in 
(xine, mplayer)

I don't see why this here would be any different.

If VIAs own driver does get reworked by fb/kernel people and included, 
then VIA will not accept these changes and will just continue things 
seperately themselves.

The fact that some backward compatibility defines were deemed 
superfluous already, and the fact that VIAs direct customers probably 
want those things to be possible for quite some time still, will mean 
that VIA will see no other option but to keep things in their own fork.

History repeating.

Luc Verhaegen.
http://unichrome.sf.net/

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

  reply	other threads:[~2007-05-06  2:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-05 14:49 [PATCH 06/20] vt8623fb: New framebuffer driver for VIA VT8623 Antonino A. Daplas
2007-05-05 18:15 ` Ville Syrjälä
2007-05-05 20:08   ` Ondrej Zajicek
2007-05-05 20:34     ` Ville Syrjälä
2007-05-05 22:48       ` Luc Verhaegen
2007-05-05 23:07         ` Antonino A. Daplas
2007-05-05 23:31           ` Luc Verhaegen
2007-05-05 23:38             ` Luc Verhaegen
2007-05-06  1:36               ` Ville Syrjälä
2007-05-06  2:07                 ` Luc Verhaegen [this message]
2007-05-05 23:03       ` Antonino A. Daplas
2007-05-08  6:28 ` Andrew Morton
2007-05-08 12:28   ` [PATCH] vt8623fb: Fix compile error if CONFIG_MTRR=n Antonino A. Daplas

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=20070506020742.GA19784@skynet.be \
    --to=libv@skynet.be \
    --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).