linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: surendra.yadav@softdel.com
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Framebuffer driver using SM501 hardware.
Date: Tue, 16 Aug 2005 12:38:50 -0400	[thread overview]
Message-ID: <3b41d8d77ede2e44e1544ccfbb780ec5@embeddededge.com> (raw)
In-Reply-To: <BPEMKMADCCCPHPEDDKOOMEHFCFAA.surendra.yadav@softdel.com>


On Aug 16, 2005, at 9:34 AM, Surendra Yadav wrote:

> 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.

I hope you didn't start from scratch.  There is already an SM501
framebuffer driver that works for both CRT and 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.

I don't think you want to do that unless you want two completely 
separate
images on the different outputs.  Normally, both the CRT and TFT display
the same images from the single framebuffer, and you use the capability
of the graphics engine to resize as necessary.

> .... 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.

If that's what you really want to do, I suspect you will have to 
register the driver
twice as two separate frame buffers and then manage that within the
single driver.  I would also consider allocating different areas of the 
single
frame buffer and then configure the planes to use the different areas 
within
the single buffer.

Good luck.


	-- Dan

  reply	other threads:[~2005-08-16 16:38 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 [this message]
2005-08-16 18:23 ` Clemens Koller
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=3b41d8d77ede2e44e1544ccfbb780ec5@embeddededge.com \
    --to=dan@embeddededge.com \
    --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).