From: "Krzysztof Helt" <krzysztof.h1@wp.pl>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: [RFC]: s3c2410fb conversion
Date: Fri, 26 Jan 2007 09:06:44 +0100 [thread overview]
Message-ID: <45b9b69474f01@wp.pl> (raw)
Hello,
The s3c2410fb driver needs register values set for every
platform. A way of conversion is to move as many values to
particular fields (e.g. resolution, bit depth, etc.) and
calculate the register values from them.
I want to ask how far one should move in conversion of the
driver. Should enumerated values also be moved to separate fields
or they can be set with "or" operator (I) into existing register
fields? I mean values (usually bits) like display type (STN/TFT
bit), etc.
E.g., the pxafb driver works with the latter approach. Most of
values are calculated but some of them are set as or-ed values
into register-like fields (the bits from fields are directly
copied to register's bits and completed by bits from calculated
values).
The s3c2410fb driver does not work currently because some
conversion started and was not finished (no platform code support
it). I need to know how to fix it - either modify platform or fb
code depending on the approach.
Regards,
Krzysztof
----------------------------------------------------
Odkryj drug± stronê ciemnego portalu - "World of War Craft" premiera:
http://klik.wp.pl/?adr=http%3A%2F%2Fadv.reklama.wp.pl%2Fas%2Fd59.html&sid=1000
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next reply other threads:[~2007-01-26 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 8:06 Krzysztof Helt [this message]
2007-02-12 10:06 ` [RFC]: s3c2410fb conversion Ben Dooks
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=45b9b69474f01@wp.pl \
--to=krzysztof.h1@wp.pl \
--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).