linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Clemens Koller <clemens.koller@anagramm.de>
To: surendra.yadav@softdel.com
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Framebuffer driver using SM501 hardware.
Date: Tue, 16 Aug 2005 20:23:01 +0200	[thread overview]
Message-ID: <43022F05.3050409@anagramm.de> (raw)
In-Reply-To: <BPEMKMADCCCPHPEDDKOOMEHFCFAA.surendra.yadav@softdel.com>

[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]

Hi!

I was working with the SM501 framebuffer for a while on
linux-2.6.

It is heavily based on old silicon motion code and
not in good shape, so I didn't dare to publish it ;-)

But it's working on ppc, linux-2.6 and X was running on it.
There is a color-mapping issue left (RGB is swapped on powerpc)
and it needs lots of code cleanup or a complete rewrite.

Due to my project schedule, it will take me some month
until I can focus on the voyagerfb again.

But take what you want...

Best greets,

Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany

http://www.anagramm.de
Phone: +49-89-741518-50
Fax: +49-89-741518-19
Surendra Yadav wrote:

> Hi all,
> 
> I am writing framebuffer driver using SM501. This graphics driver chip can
> drive CRT and TFT panel. I have written two seperate framebuffer driver, one
> for CRT and one for TFT Panel.
> 
> But I am not able to test both the devices. Any one of them work at a time.
> I have created two files /dev/fb0 and /dev/fb1. These two can be open
> successfully and mmap is also successful from userspace. If I am trying to
> write on fb0 and  fb1 with different data, they displayed on either CRT or
> TFT panel.
> 
> Can any one help me How to test two different framebuffer devices?
> 
> Thanks.
> 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
> 

[-- Attachment #2: voyager-0.2.tar.gz --]
[-- Type: application/octet-stream, Size: 25402 bytes --]

  parent reply	other threads:[~2005-08-16 18:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 13:34 Framebuffer driver using SM501 hardware Surendra Yadav
2005-08-16 16:38 ` Dan Malek
2005-08-16 18:23 ` Clemens Koller [this message]
2005-08-16 19:48   ` Wolfgang Denk
2005-08-17 10:11     ` [F]Framebuffer " Andrey Volkov
2005-08-17 11:04       ` Clemens Koller
2005-08-17 11:50         ` Matej Kupljen
2005-08-17 12:37           ` Andrey Volkov
2005-08-17 11:18       ` Geert Uytterhoeven
2005-08-17 12:15         ` Andrey Volkov
2005-08-17 12:42           ` Geert Uytterhoeven
2005-08-17 14:23             ` Andrey Volkov
2005-08-17 14:31             ` Clemens Koller
2005-08-17 14:52               ` Andrey Volkov
2005-08-16 19:42 ` Framebuffer " Wolfgang Denk

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=43022F05.3050409@anagramm.de \
    --to=clemens.koller@anagramm.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=surendra.yadav@softdel.com \
    /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).