linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "L.Y.Mesentsev" <L.Mesentsev@tvfiles.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: TVIA CyberPro 5005 problem
Date: Tue, 12 Nov 2002 10:52:24 +0000	[thread overview]
Message-ID: <3DD0DD68.2070005@tvfiles.com> (raw)

Hi All,

Recently I've purchased a  settopbox from AllWell  ( 
http://www.gctglobal.com/Products/Set_Top_Box/Metallic6086N2/metallic6086n2.html 
)
equipped with  TVIA CyberPro 5005 chipset.  In order to use it with 
DirectFB + VDR under Linux I'm looking for framebuffer driver for it. 
 The only driver I've found is cyber2000fb available with a current 
kernels and it claims to support  ex-IGS (now TVIA) CyberPro 5000 
chipsets, that should be compatible with 5005 chipsets ( I have a full 
complete documentation on my chipset and it seems to be true ). The 
problem is that after cyber2000fb.o is correctly loaded into the kernel 
( it properly recognizes 500X chipset, video memory amount and don't log 
warnings either errors ) - I see a white square on the screen ( ~ 
640x480 on 720x576 )  traced with weird green diagonal lines. When I try 
to launch any example from DirectFB ( 640x480x16 60Hz for instance )  - 
the screen becomes flicking and  BW, but I can see the graphic output ( 
images & animation ).
Unfortunately I have not enough skill to solve this problem myself, but 
I have a full set of documentation for 500X chipset and  big desire to 
learn.

Please, help me to make this  chipset work  -  any help will be 
appreciated.  





-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing 
your web site with SSL, click here to get a FREE TRIAL of a Thawte 
Server Certificate: http://www.gothawte.com/rd524.html

                 reply	other threads:[~2002-11-12  9:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3DD0DD68.2070005@tvfiles.com \
    --to=l.mesentsev@tvfiles.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).