linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: Jens Schmalzing <j.s@lmu.de>,
	linux-fbdev-devel@lists.sourceforge.net,
	debian-kernel@lists.debian.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [patch, 2.6, ppc] some modular framebuffer support
Date: Thu, 1 Jul 2004 13:34:21 +0200	[thread overview]
Message-ID: <20040701113421.GA9187@pegasos> (raw)
In-Reply-To: <hh4qosi15h.fsf@alsvidh.mathematik.uni-muenchen.de>


Let's bring linux-fbdev in the loop, as they probably are the best
placed to comment.

On Thu, Jul 01, 2004 at 10:26:18AM +0200, Jens Schmalzing wrote:
> Hi,
>
> the following patch allows some accelerated framebuffers (aty128fb,
> atyfb, radeonfb, and rivafb) and framebuffer console support itself to
> be built as modules on ppc.  Tested on a Powerbook Pismo, works very
> well including XFree86 and DRI.
>
> The first hunk suppresses a warning only, not sure about it.

Jens, i am not sure of the wisdom of pursuing this way. I know that
modularizing stuff and even fbdev drivers is a good thing, but i also
know that you plan to use this to modularize most fbdevs out of the
debian powerpc kernel.

I wonder at the implications, since modular fbdevs are loaded well later
than non-modular ones, and we thus lose lots of early log messages,
which may be ok for us hackers with a serial console ready to catch
them, but may be a nightmare for general users of the debian powerpc
package, not to speak about us who will have to do the support job on
those.

linux-fbdev folk, what is your take on this, would it be possible to
somehow get a way to have earlier debug messages, or to bring the
loading of fbdev modules to an earlier point ? Benh, where you working
on something such ? I think i remember something about this mentioned.

Or maybe i am wrong, and using a modular fbdev on a not offb supporting
powerpc is just fine.

Friendly,

Sven Luther

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

       reply	other threads:[~2004-07-01 11:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <hh4qosi15h.fsf@alsvidh.mathematik.uni-muenchen.de>
2004-07-01 11:34 ` Sven Luther [this message]
2004-07-01 14:47   ` [Linux-fbdev-devel] Re: [patch, 2.6, ppc] some modular framebuffer support David Eger

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=20040701113421.GA9187@pegasos \
    --to=sven.luther@wanadoo.fr \
    --cc=debian-kernel@lists.debian.org \
    --cc=j.s@lmu.de \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linuxppc-dev@lists.linuxppc.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 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).