linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <luther@dpt-info.u-strasbg.fr>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: video dir reorg
Date: Tue, 14 Jan 2003 22:26:47 +0100	[thread overview]
Message-ID: <20030114212646.GA3731@iliana> (raw)
In-Reply-To: <20030114172236.69468.qmail@web14905.mail.yahoo.com>

On Tue, Jan 14, 2003 at 09:22:36AM -0800, Jon Smirl wrote:
> --- Sven Luther <luther@dpt-info.u-strasbg.fr> wrote:
> > I think Linus rejected this last time James
> > submitted it.
> 
> Didn't the last patch just move the DRM directory from
> driver/char into the video directory.?

There is a response of linus in the mailing list archive about this, i
don't remember nor checked if it was only the first time, or not. I
think the objection was about complicate to supervise diffs.

> This could be done in two steps. First split out the
> fb console driver files into their own directory and
> then sort out the hardware drivers more. Then if the
> DRM merge gets ok'd everything will be ready.
> 
> In the config system I don't like how you have to
> enable driver support for the same piece of hardware
> in two different places. I also don't like looking in
> two different places for the source to drivers for the
> same hardware.
> 
> What is Linus' take on merging a card's fb and drm
> drivers into a single module in the long run?

Well, the problem is that the fb drivers are maintained by us, and the
drm drivers are maintained by the DRI.

Also, i think the drm drivers should compile not only on linux, but on
other oses too (BSDs at least).

Also, i believe some of the XFree86 guys don't like fbdevs.

Friendly,

Sven Luther


-------------------------------------------------------
This SF.NET email is sponsored by: Take your first step towards giving 
your online business a competitive advantage. Test-drive a Thawte SSL 
certificate - our easy online guide will show you how. Click here to get 
started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en

  reply	other threads:[~2003-01-14 21:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14  2:02 video dir reorg Jon Smirl
2003-01-14  9:13 ` Sven Luther
2003-01-14 17:22   ` Jon Smirl
2003-01-14 21:26     ` Sven Luther [this message]
2003-01-15  0:37       ` James Simmons
2003-01-15  9:39         ` Geert Uytterhoeven
2003-01-15 21:38         ` Michel Dänzer
     [not found]           ` <20030116035231.36507.qmail@web14910.mail.yahoo.com>
2003-01-16 10:38             ` Sven Luther
2003-01-16 20:14             ` 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=20030114212646.GA3731@iliana \
    --to=luther@dpt-info.u-strasbg.fr \
    --cc=jonsmirl@yahoo.com \
    --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).