LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Claus Gindhart <Claus.Gindhart@kontron.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: Tue, 14 Jan 2003 08:46:56 +0100	[thread overview]
Message-ID: <21A8AE56EBB6D411A4520060973D360101A9F739@PEPINTERCOM> (raw)


Hello John,

i assume you want to see console output on the framebuffer
device.
To achieve this, you need
the framebuffer driver
  from your mail i conclude, that You have a framebuffer driver
a keyboard driver
  the dummy keyboard driver is o.k., if you dont have a physical kbd
Additionally you have to enable CONFIG_VT and CONFIG_VT_CONSOLE
on your system.
Please remove console=ttyS0 from the kernel command line. Put a console=xxx
command, which is appropriate for your framebuffer driver (see sourcecode
of framebuffer driver)

-----Original Message-----
From: Gallant, John [mailto:jgallant@vanteon.com]
Sent: Montag, 13. Januar 2003 17:23
To: linuxppc-embedded@lists.linuxppc.org
Subject: Assistance with using /dev/fb0 and No X windows

    I have managed to get the "default" VGA/FB support to access my graphics
device on the onboard PCI bus.  We a SMI LynxEM chip on the board.  I have
the vga init() code properly accessing the device and the on chip frame
buffer.  I have used fbset to determine if /dev/fb0 can be accessed, and the
driver is called.  I also tried "ls -l > /dev/fb0" this also gets into the
vga16fb_get_fix() code.

    What I need to do, and here is my lack of understanding, is to have some
program access the /dev/fb0 device and display on the CRT.  I do not have
any X support, only whatever came with the MVL distribution.  I am wondering
what is necessary to use mingetty, or some other display method.

    Added wrinkles:  No keyboard yet, but I do have the console=ttyS0
working.

    So any advice on what I could use or what I may have missed in my
Xconfig settings?
[...]

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2003-01-14  7:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14  7:46 Claus Gindhart [this message]
2003-01-14 17:27 ` Assistance with using /dev/fb0 and No X windows Chirag Kantharia
  -- strict thread matches above, loose matches on Subject: below --
2004-02-13 16:50 llandre
2003-01-14 22:17 Gallant, John
2003-01-15  3:55 ` Chirag Kantharia
2003-01-15 10:32 ` Mark Powell
2003-01-15 11:38   ` David Gibson
2003-01-15 12:28     ` Mark Powell
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=21A8AE56EBB6D411A4520060973D360101A9F739@PEPINTERCOM \
    --to=claus.gindhart@kontron.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