From: Clemens Koller <clemens.koller@anagramm.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Silicon Motion SM501 Voyager GX fb driver development
Date: Thu, 09 Dec 2004 11:44:45 +0100 [thread overview]
Message-ID: <41B82C9D.7040105@anagramm.de> (raw)
Hello!
Well, I am about to implement a fbdev for the Silicon Motion Inc.'s
SM501 (alias Voyager GX) embedded graphics controller for our
next projects. (http://www.siliconmotion.com/sm501.htm)
The goal is to get a stable fb up and running on a current Kernel 2.6.x
The Platform is currently a PowerMac G4 Windtunnel (CRUX PPC 2.0)
and later on it will be a Freescale MPC8540 embedded processor.
The SM501 hardware is the PCI Demo Board from SMI.
I've started from the latest ix86 released driver from SMI and I
got some basic functionality working. (There appears some (sometimes
garbled) image on the panel, driver has memory leaks, as there are
pci_resource and ioremap problems ...)
So, the point is, I want to "fix" or better re-write the code
from SMI to get an up-to-date driver for Kernel 2.6.
My question is: Where is a good way to start to learn from
already existing code? radeonfb or aty128fb or which driver
is the most current and Kernel 2.6 aware driver.
Later on I will also need to implement power management and
try to get the other SM501 peripherals working (USB, Audio,
Touchpanel,...)
It's my first framebuffer thing I do, so there might be some
novice questions or completely ungeek mistakes.
Currently I want to fix the module load/unload (ioremap/iounmap)
thing if ioremap is really the current way to do it.
For sure, you can get my code if you want. But it's still in
pretty ugly condition.
Best greets,
--
Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany
http://www.anagramm.de
Phone: +49-89-741518-50
Fax: +49-89-741518-19
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next reply other threads:[~2004-12-09 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 10:44 Clemens Koller [this message]
2004-12-09 20:01 ` Silicon Motion SM501 Voyager GX fb driver development Antonino A. Daplas
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=41B82C9D.7040105@anagramm.de \
--to=clemens.koller@anagramm.de \
--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).