Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: geert@linux-m68k.org
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-fbdev@vger.kernel.org
Subject: Re: [GIT]: Sparc
Date: Sun, 14 Mar 2010 21:24:12 +0000	[thread overview]
Message-ID: <20100314.142412.52181590.davem@davemloft.net> (raw)
In-Reply-To: <10f740e81003140734p30959952ld4563d2b22d834af@mail.gmail.com>

From: Geert Uytterhoeven <geert@linux-m68k.org>
Date: Sun, 14 Mar 2010 15:34:03 +0100

> On Sun, Mar 14, 2010 at 03:17, David Miller <davem@davemloft.net> wrote:
>> David S. Miller (1):
>>      sparc64: Add very basic XVR-1000 framebuffer driver.
> 
> Have you ever looked into getting offb to work on sparc64?

Can't for several of these drivers.

For example, the svr500 comes up in some kind of striped plane mode so
we have to write every pixel to two planes of the frame buffer.

Also offb doesn't know the implied endianness of the framebuffer.  UPA
based framebuffers are typically big endian, whereas most (but not
all) PCI are little-endian.

I also intend to get these thing supporting accelerated at some
pointer.

offb looks like a big hack instead of something generic that
could support any framebuffer that adheres to the standard
openfirmware framebuffer device properties.  It's just using
a bunch of properties created internally by bootx.

      reply	other threads:[~2010-03-14 21:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100313.181754.107699673.davem@davemloft.net>
2010-03-14 14:34 ` [GIT]: Sparc Geert Uytterhoeven
2010-03-14 21:24   ` David Miller [this message]

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=20100314.142412.52181590.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox