linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Akhilesh Soni" <akhilesh@innomedia.soft.net>
To: <linuxppc-embedded@ozlabs.org>
Subject: Advice on Linux Framebuffer driver implemetation
Date: Wed, 4 Apr 2007 11:49:42 +0530	[thread overview]
Message-ID: <004d01c77681$3bdbae60$0a12a8c0@innomedia> (raw)

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

Hello,

I want advice on how to proceed for the following problem 

As per my knowledge the Linux frame buffer requires the pixel data to be in a packed pixel contiguous buffer. This means that the all the data for one pixel must be packed together, followed by the data for the next pixel, etc.(please correct me if I'm wrong)

 On my Set-top-box hardware Vulcan (IBM ppc405),  the best resolution supported  in this packed pixel format is 8bpp color table format. Vulcan resolutions above the 8bpp color table resolution  require separate  luma and chroma buffers,  where the hardware expects all the luma values to be in one buffer and all chroma values to be in another buffer. Since the data for the resolutions above 8bpp are required by the hardware to be in separate luma and chroma buffers it does not meet the LInux Frame buffer requirement of packed pixel data. 

Now how can I overcome this limitation where graphics H/W expects separate Luma and Chroma buffers whereas linux framebuffer expect all things packed. Is there any such driver already present which I can study to overcome such limitation.

I'm using Montavista linux kernel 2.4.20 on IBM stb0x25xxx(ppc405 core).

Regards,
Akhilesh 


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


[-- Attachment #2: Type: text/html, Size: 2361 bytes --]

             reply	other threads:[~2007-04-04  6:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-04  6:19 Akhilesh Soni [this message]
2007-04-05 23:13 ` Advice on Linux Framebuffer driver implemetation Carlos Munoz

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='004d01c77681$3bdbae60$0a12a8c0@innomedia' \
    --to=akhilesh@innomedia.soft.net \
    --cc=linuxppc-embedded@ozlabs.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).