linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Romain Dolbeau <dolbeau@irisa.fr>
To: Chris Wilson <chris@qwirx.com>
Cc: Linux Kernel Janitors
	<kernel-janitor-discuss@lists.sourceforge.net>,
	Trivial Patch Monkey <trivial@rustcorp.com.au>,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] save_flags/cli in drivers/video/pm3fb.c
Date: Mon, 25 Nov 2002 11:01:15 +0100	[thread overview]
Message-ID: <3DE1F4EB.2050207@irisa.fr> (raw)
In-Reply-To: Pine.LNX.4.44.0211232001050.15858-200000@top.qwarx.com

Chris Wilson wrote:

> Since I can't compile this driver on my architecture, I'm afraid I haven't 
> been able to test this patch at all.

This patch is relevant for 2.5.x only, and pm3fb can't compile
and work on 2.5.x. The FB API was changed, and FB drivers
need to be rewritten. As I never found a 2.5.x release that
would compile on my box (no x86 here), I didn't port pm3fb.

BTW, pm3fb should not be integrated in 2.5.x, it was submitted
only to 2.4.x and somehow found its way in 2.5.x. I don't
maintain pm3fb on 2.5.x, never has, and likely never will.

The proper fix for pm3fb in 2.5 is to delete it, at least
until someone else rewrite it or until 2.5.x can actually
compile and work on PowerPC and I can rewrite it myself.

-- 
romain



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

       reply	other threads:[~2002-11-25 10:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0211232001050.15858-200000@top.qwarx.com>
2002-11-25 10:01 ` Romain Dolbeau [this message]
2002-11-25 17:53   ` [Linux-fbdev-devel] Re: [PATCH] save_flags/cli in drivers/video/pm3fb.c Sven Luther
2002-11-26 23:38     ` James Simmons
2002-11-27  7:26       ` Sven Luther
2002-11-27 17:43         ` James Simmons
2002-11-27  0:52   ` 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=3DE1F4EB.2050207@irisa.fr \
    --to=dolbeau@irisa.fr \
    --cc=chris@qwirx.com \
    --cc=kernel-janitor-discuss@lists.sourceforge.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=trivial@rustcorp.com.au \
    /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).