linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antonino Daplas <adaplas@pol.net>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Hartmut Van Waregem <hvanwaregem@yahoo.com>
Subject: [Fwd: [directfb-dev] Is is eady to improve / extend 5005 driver]
Date: 17 Feb 2003 14:32:21 +0800	[thread overview]
Message-ID: <1045463288.1207.26.camel@localhost.localdomain> (raw)

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




[-- Attachment #2: Forwarded message - [directfb-dev] Is is eady to improve / extend 5005 driver --]
[-- Type: message/rfc822, Size: 3544 bytes --]

From: Hartmut Van Waregem <hvanwaregem@yahoo.com>
To: directfb-dev@directfb.org
Subject: [directfb-dev] Is is eady to improve / extend 5005 driver
Date: Tue, 11 Feb 2003 14:20:59 -0800 (PST)
Message-ID: <20030211222059.99232.qmail@web20710.mail.yahoo.com>

Hi,

I am trying to implement a new application for the
OpenBrick (www.openbrick.org) which is based on the
IGS 5005 chipset.

I tried many binary drivers from TVIA (available here
or there on the Web) which are all more a less buggy.
Also, apparently, TVIA does not open source the
drivers and requires a very high amount of money to
provide source code from what I read on this mailing
list. I have contacted the people at Nexedi who
distribute the OpenBrick but they told me that they
were not allowed yet to distribute the binary driver
which TVIA provided them and that they were still
waiting for TVIA to allow them to do so. They advised
me to use VESA until TVIA would provide them a good
support. 

Therefore, I would prefer to support the kernel GPL
driver for IGS 5005 by developing my application based
on this driver rather than supporting the TVIA
proprietary approach.

I have already been evaluating the kernel fb driver
which works quite OK on the OpenBrick but does not
seem to be able to initialize the 4MB shared memory,
thus preventing high resolutions / high depth. I will
try this WE to patch  it somehow to get the 4MB.
Besides that, scrolling generates many strange small
pixels in high res (it is OK in low res). And some
features of the IGS 5005 do not seem to be
implemented.

What I need for my application(s) is
	- get good resolution (ie. 1280 x 1024 in 16 bits)
	- be able to display a small MPEG stream (from a
file) on the TV output and a Web Page on the VGA
output at the same time

I would really appreciate if someone could let me know
if all this is possible / easy / complex etc. to
implement based on either directfb and/or the linux
framebuffer driver.

Regards,

Hartmut.

__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com


-- 
Info:  To unsubscribe send a mail to ecartis@directfb.org with 
"unsubscribe directfb-dev" as subject.


                 reply	other threads:[~2003-02-17  6:32 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=1045463288.1207.26.camel@localhost.localdomain \
    --to=adaplas@pol.net \
    --cc=hvanwaregem@yahoo.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=rmk@arm.linux.org.uk \
    /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).