All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@convergence.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: James Simmons <jsimmons@infradead.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: fbdv/fbcon pending problems
Date: Mon, 23 Feb 2004 16:52:09 +0100	[thread overview]
Message-ID: <20040223155209.GB302@convergence.de> (raw)
In-Reply-To: <1077497593.5960.28.camel@gaston>

Benjamin Herrenschmidt wrote:
> 
> Here's a list of pending issues with fbdev (either upstream or in the
> fbdev bk treee), I figured posting it here may help getting more people
> on those issues as my time is sparse and I suppose James too.
...
> Ok, that's all that comes to my mind right now, help is welcome :)

IMHO it is rather discouraging that:

FRAMEBUFFER LAYER
P:      James Simmons, Geert Uytterhoeven       
M:      jsimmons@infradead.org, geert@linux-m68k.org    
L:      linux-fbdev-devel@lists.sourceforge.net 
W:      http://www.linux-fbdev.org

$ host www.linux-fbdev.org
Nameserver not responding
www.linux-fbdev.org A record not found, try again


http://linux-fbdev.sourceforge.net/ has no halfway up-to-date information about
the state of 2.6 fbdev devlopment. Sure, one can dig through the mailing list
archives, but if a project is looking for developers I would at least expect a
link to
- the current fbdev source tree
- a TODO that lets me see what work is currently been done by others,
  and what work could be contributed by me

(This is just a suggestion, I don't have time to work on fbdev myself.)

Johannes

  reply	other threads:[~2004-02-23 15:52 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23  0:53 fbdv/fbcon pending problems Benjamin Herrenschmidt
2004-02-23  0:53 ` Benjamin Herrenschmidt
2004-02-23 15:52 ` Johannes Stezenbach [this message]
2004-02-23 18:59 ` James Simmons
2004-02-23 22:50   ` Benjamin Herrenschmidt
2004-02-23 22:50     ` Benjamin Herrenschmidt
2004-02-24  1:19     ` James Simmons
2004-02-24  1:19       ` James Simmons
2004-02-24  8:37     ` Geert Uytterhoeven
2004-02-24  8:37       ` [Linux-fbdev-devel] " Geert Uytterhoeven
2004-02-24  8:33       ` Benjamin Herrenschmidt
2004-02-24  8:33         ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2004-02-23 20:35 ` Thorsten Kranzkowski
2004-02-23 22:18   ` James Simmons
2004-02-23 22:18     ` James Simmons
2004-02-24  2:37 ` Otto Solares
2004-02-24  2:37   ` [Linux-fbdev-devel] " Otto Solares
2004-02-24  8:35   ` Geert Uytterhoeven
2004-02-24  8:35     ` [Linux-fbdev-devel] " Geert Uytterhoeven
2004-02-24 17:21     ` James Simmons
2004-02-24 21:41     ` Otto Solares
2004-02-25  1:21       ` James Simmons
2004-02-25  1:21         ` [Linux-fbdev-devel] " James Simmons
2004-02-25  1:26         ` Benjamin Herrenschmidt
2004-02-25  1:26           ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2004-02-25 21:24           ` James Simmons
2004-02-25 21:24             ` [Linux-fbdev-devel] " James Simmons
2004-02-25 23:46             ` Benjamin Herrenschmidt
2004-02-25 23:46               ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2004-02-26  0:20               ` James Simmons
2004-02-26  0:20                 ` [Linux-fbdev-devel] " James Simmons
2004-02-26  0:33                 ` Benjamin Herrenschmidt
2004-02-26  0:33                   ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2004-02-26  1:11                   ` James Simmons
2004-02-25  1:29         ` Benjamin Herrenschmidt
2004-02-25  1:29           ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2004-02-25  2:18           ` Otto Solares
2004-02-25  2:18             ` [Linux-fbdev-devel] " Otto Solares
2004-02-25  2:33             ` Benjamin Herrenschmidt
2004-02-25  2:33               ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2004-02-25  3:15         ` Otto Solares
2004-02-25  3:15           ` [Linux-fbdev-devel] " Otto Solares
2004-02-25 11:41           ` Geert Uytterhoeven
2004-02-25 11:41             ` [Linux-fbdev-devel] " Geert Uytterhoeven
2004-02-25 14:01             ` Sven Luther
2004-02-25 14:01               ` [Linux-fbdev-devel] " Sven Luther
2004-02-25 14:08               ` Geert Uytterhoeven
2004-02-25 14:08                 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2004-02-25 21:43             ` James Simmons
2004-02-25 21:43               ` [Linux-fbdev-devel] " James Simmons
2004-02-26 19:40             ` Otto Solares
2004-02-26 19:40               ` [Linux-fbdev-devel] " Otto Solares
2004-02-26 19:45               ` James Simmons
2004-02-26 19:45                 ` [Linux-fbdev-devel] " James Simmons
2004-02-26 20:12                 ` Otto Solares
2004-02-26 20:12                   ` [Linux-fbdev-devel] " Otto Solares
2004-02-25 21:42           ` James Simmons
2004-02-25 21:42             ` [Linux-fbdev-devel] " James Simmons
2004-02-26 15:26           ` Michel Dänzer
2004-02-26 15:26             ` Michel Dänzer
2004-02-24  5:57 ` Stuart Young
2004-02-24  5:57   ` Stuart Young
2004-02-24  8:36   ` Geert Uytterhoeven
2004-02-24  8:36     ` [Linux-fbdev-devel] " Geert Uytterhoeven
2004-02-25  7:14     ` Stuart Young
2004-02-25  7:14       ` [Linux-fbdev-devel] " Stuart Young
2004-02-26 15:11       ` Michel Dänzer
2004-02-26 15:11         ` Michel Dänzer

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=20040223155209.GB302@convergence.de \
    --to=js@convergence.de \
    --cc=benh@kernel.crashing.org \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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.