All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Buell <alex.buell@munted.org.uk>
To: sparclinux@vger.kernel.org
Subject: Re: XVR-500
Date: Sun, 14 Nov 2010 13:27:30 +0000	[thread overview]
Message-ID: <1289741250.10953.5.camel@lithium> (raw)
In-Reply-To: <1289604206.26034.53.camel@lithium>

[Added sparclinux@vger.kernel.org]

On Fri, 2010-11-12 at 15:27 -0800, David Miller wrote:
> From: Alex Buell <alex.buell@munted.org.uk>
> Date: Fri, 12 Nov 2010 23:15:09 +0000
> 
> > On Fri, 2010-11-12 at 12:56 -0800, David Miller wrote:
> > 
> >> That's why we need to override ->imageblit(), ->fillrect(), and
> >> ->copyarea() driver operations and can't just use the normal cfb* ones
> >> directly.
> >> 
> >> Therefore the X11 fbdev driver is never going to work properly, no
> >> matter what BPP or resolution you bring up the screen.
> > 
> > That's what I'm trying to understand - the console looks and works just
> > fine yet when the fbdev driver is loaded it doesn't get things right? I
> > thought it just run on top of the console driver? 
> 
> Nope, fbdev mmap()'s the framebuffer and writes directly to it.
> It doesn't use the console driver for anything other than mapping
> the framebuffer into the X server process's address space.

Since the console driver seems to work just fine, perhaps a new X11
driver might need to be written, using the wcfb driver from [Open|
Net]BSD as a reference. 

I will need to install OpenBSD on a spare disk and see how it works.
-- 
Tactical Nuclear Kittens

  reply	other threads:[~2010-11-14 13:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12 23:23 XVR-500 Alex Buell
2010-11-14 13:27 ` Alex Buell [this message]
2010-11-14 18:42 ` XVR-500 David Miller
2010-11-21  2:11 ` XVR-500 Alex Buell
2010-12-06  0:02 ` XVR-500 Alex Buell
2010-12-06  0:05 ` XVR-500 Alex Buell
2010-12-06  2:34 ` XVR-500 David Miller

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=1289741250.10953.5.camel@lithium \
    --to=alex.buell@munted.org.uk \
    --cc=sparclinux@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.