From: Suresh Chandra Mannava <Mannava@GameBox.net>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: implementing vga16fb
Date: Tue, 23 Mar 2004 10:58:32 +0530 [thread overview]
Message-ID: <405FCB00.2070601@GameBox.net> (raw)
Dear Friends,
I am a new to framebuffer, we are implementing kernel framebuffer
support for the new CPU architecture. I have some basic questions
related to vga16fb. Please provide some inputs and drive us for
successful implementation of framebuffer.
Even though we are having PCI ATI Rage XL graphic card, we are
interested in implementing generic vga16fb for an initial test.
Here are my few queries,
I read that VESAfb is only for Intel(x86) platforms, has any body
implemented Vesafb on other platforms?
Is vga16fb a CPU architecture dependent? Even though I didn't find any
architecture dependent sections in the code, Is there any code section
that to be modified in vga16fb.c?
What are the corresponding files need to be modified for implementing
framebuffer support for newer platforms.
And lastly, we are testing this framebuffer on 2.6Mhz FPGA(0.16
Bogomips) with kernel 2.4.7. Are there any other methods (solutions) for
debugging framebuffer code with out using printk's?
I request your help.
Regards,
Suresh Chandra Mannava.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next reply other threads:[~2004-03-23 5:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 5:28 Suresh Chandra Mannava [this message]
2004-03-23 9:47 ` implementing vga16fb Geert Uytterhoeven
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=405FCB00.2070601@GameBox.net \
--to=mannava@gamebox.net \
--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).