All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: James Simmons <jsimmons@www.infradead.org>
Cc: Jon Smirl <jonsmirl@gmail.com>, Dave Airlie <airlied@gmail.com>,
	James Simmons <jsimmons@pentafluge.infradead.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	adaplas@pol.net, dri-devel@lists.sourceforge.net,
	xorg@lists.freedesktop.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] Resource management.
Date: Tue, 22 Feb 2005 13:59:22 -0500	[thread overview]
Message-ID: <a728f9f90502221059686284a7@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0502221719440.30102@pentafluge.infradead.org>

On Tue, 22 Feb 2005 17:23:03 +0000 (GMT), James Simmons
<jsimmons@www.infradead.org> wrote:
> 
> > As far as I know none of the significant contributors on either fbdev
> > or DRM are being paid to work on the project.
> 
> So I have noticed. There is much to do but no real man power. We are
> talking about this merging but at our rate it will take 5 years to happen.
> We don't have the man power to do this. So I'm not going to bother
> merging. Its all pipe dreams here.
> 
> 

with that attitude it's never gonna happen.  I work almost exclusively
on X, but once we get at least one sample driver done (probably
radeon, I would be more than happy to devote my limited development
resources to the new drm/fb super driver.  Right now the kernel FB
drivers have no benefit for me so I don't use/develop them.  The drm
just works and I'm more interested in the crtc/modes/outputs handling
than the command processor control stuff.  I think a lot of X
developers (and porobably IHVs) will get on board when this happens. 
X is undermanned as well, but we've managed to do a pretty good job of
supported a lot of features on a fair number of cards.

Alex


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
--

WARNING: multiple messages have this Message-ID (diff)
From: Alex Deucher <alexdeucher@gmail.com>
To: James Simmons <jsimmons@www.infradead.org>
Cc: Jon Smirl <jonsmirl@gmail.com>, Dave Airlie <airlied@gmail.com>,
	James Simmons <jsimmons@pentafluge.infradead.org>,
	Linux Fbdev development list 
	<linux-fbdev-devel@lists.sourceforge.net>,
	adaplas@pol.net, dri-devel@lists.sourceforge.net,
	xorg@lists.freedesktop.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] Resource management.
Date: Tue, 22 Feb 2005 13:59:22 -0500	[thread overview]
Message-ID: <a728f9f90502221059686284a7@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0502221719440.30102@pentafluge.infradead.org>

On Tue, 22 Feb 2005 17:23:03 +0000 (GMT), James Simmons
<jsimmons@www.infradead.org> wrote:
> 
> > As far as I know none of the significant contributors on either fbdev
> > or DRM are being paid to work on the project.
> 
> So I have noticed. There is much to do but no real man power. We are
> talking about this merging but at our rate it will take 5 years to happen.
> We don't have the man power to do this. So I'm not going to bother
> merging. Its all pipe dreams here.
> 
> 

with that attitude it's never gonna happen.  I work almost exclusively
on X, but once we get at least one sample driver done (probably
radeon, I would be more than happy to devote my limited development
resources to the new drm/fb super driver.  Right now the kernel FB
drivers have no benefit for me so I don't use/develop them.  The drm
just works and I'm more interested in the crtc/modes/outputs handling
than the command processor control stuff.  I think a lot of X
developers (and porobably IHVs) will get on board when this happens. 
X is undermanned as well, but we've managed to do a pretty good job of
supported a lot of features on a fair number of cards.

Alex

  reply	other threads:[~2005-02-22 18:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21 19:11 Resource management James Simmons
2005-02-21 22:53 ` Antonino A. Daplas
2005-02-21 23:25   ` James Simmons
2005-02-22  1:01     ` Jon Smirl
2005-02-22  3:53       ` James Simmons
2005-02-22  3:53         ` [Linux-fbdev-devel] " James Simmons
2005-02-22  4:46         ` Dave Airlie
2005-02-22  5:13           ` James Simmons
2005-02-22  5:13             ` [Linux-fbdev-devel] " James Simmons
2005-02-22  5:59             ` Jon Smirl
2005-02-22  5:59               ` Jon Smirl
2005-02-22  5:23           ` Jon Smirl
2005-02-22  5:23             ` Jon Smirl
2005-02-22 17:23             ` James Simmons
2005-02-22 17:23               ` [Linux-fbdev-devel] " James Simmons
2005-02-22 18:59               ` Alex Deucher [this message]
2005-02-22 18:59                 ` Alex Deucher
2005-02-22 13:25     ` Antonino A. Daplas
2005-02-22 14:06     ` Antonino A. Daplas
2005-02-24 19:57       ` James Simmons
2005-02-24 23:05         ` Antonino A. Daplas
2005-02-28 20:01           ` Resource management II James Simmons

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=a728f9f90502221059686284a7@mail.gmail.com \
    --to=alexdeucher@gmail.com \
    --cc=adaplas@pol.net \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=geert@linux-m68k.org \
    --cc=jonsmirl@gmail.com \
    --cc=jsimmons@pentafluge.infradead.org \
    --cc=jsimmons@www.infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xorg@lists.freedesktop.org \
    /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.