From: Chirag Kantharia <kantharia@hathway.com>
To: "Gallant, John" <jgallant@vanteon.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Assistance with using /dev/fb0 and No X windows
Date: Wed, 15 Jan 2003 09:25:12 +0530 [thread overview]
Message-ID: <20030115092512.A809@toxic> (raw)
In-Reply-To: <4926614F7A31D411820F00D0B74FF7E0013D1A21@RDC03>; from jgallant@vanteon.com on Tue, Jan 14, 2003 at 05:17:22PM -0500
On Tue, Jan 14, 2003 at 05:17:22PM -0500, Gallant, John wrote:
| 2) Does anyone know of a driver for the LynxEM chip that is not from the
| XFree86 code base?
There is lynxfb.c in the linuxppc_2_4_devel tree
(http://www.penguinppc.org/dev/kernel.shtml). You can use that as the
starting point. It's a WIP.
| I am planning to "strategically advance to the rear" and go back to the
| PPCBoot code where I was able to get a few bands of color when the LOGO was
| supposed to be drawn on the screen. If I can get that to work I am hoping
| that I can form a better understanding of the LynxEM chip to either create a
| limited driver or hack up the vga16fb.c file some more before I work on a
| limited driver.
A working fbset just proves that you are able to talk to the framebuffer
support in the kernel. It doesn't indicate that your framebuffer is
actually able to talk to your hardware.
--
Chirag Kantharia, symonds.net/~chyrag/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-15 3:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 22:17 Assistance with using /dev/fb0 and No X windows Gallant, John
2003-01-15 3:55 ` Chirag Kantharia [this message]
2003-01-15 10:32 ` Mark Powell
2003-01-15 11:38 ` David Gibson
2003-01-15 12:28 ` Mark Powell
-- strict thread matches above, loose matches on Subject: below --
2004-02-13 16:50 llandre
2003-01-14 7:46 Claus Gindhart
2003-01-14 17:27 ` Chirag Kantharia
2003-01-13 16:23 Gallant, John
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=20030115092512.A809@toxic \
--to=kantharia@hathway.com \
--cc=jgallant@vanteon.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).