From: David Gibson <david@gibson.dropbear.id.au>
To: Bai Shuwei <baishuwei@gmail.com>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: Re: powerpc 440 monitor program
Date: Fri, 19 Oct 2007 13:49:04 +1000 [thread overview]
Message-ID: <20071019034904.GA4407@localhost.localdomain> (raw)
In-Reply-To: <f3566d60710182032h69e2d2bejafd96f18dae95829@mail.gmail.com>
On Fri, Oct 19, 2007 at 11:32:33AM +0800, Bai Shuwei wrote:
> all,
> hi, when I boot my system, there are no output on the screen.
> I choice the framebuffer and my monitor card is ATI PAGE 128 PCI, qt/e GUI.
> When i compile the kernel, the boot logo and aty 128fb has be compiled into
> kernel patched with videoboot, and x86emu. The video parameters set:
> video=aty128fb:640x480-16@7.
> The kenel can recognize the monitor card, and the frame buffer device
> has run.
> The output showed below:
>
> videoboot: Booting PCI video card bus 0, function 0, device 6
> aty128fb: Found Intel x86 BIOS ROM Image
> aty128fb: Rage128 BIOS located
> aty128fb: Rage128 RK PCI [chip rev 0x2] 32M 64-bit SDR SGRAM (2:1)
> fb0: ATY Rage128 frame buffer device on Rage128 RK PCI
>
> My problem is there is no output on the monitor,and cannot see the penguin
> boot logo.
Uh.. most 440 systems use a serial console. It ought in theory to be
possible to use a framebuffer instead, but it wouldn't surprise me if
rather a lot of debugging was necessary.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-10-19 3:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 3:32 powerpc 440 monitor program Bai Shuwei
2007-10-19 3:49 ` David Gibson [this message]
2007-10-19 15:51 ` Leonid
2007-10-19 16:45 ` Olof Johansson
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=20071019034904.GA4407@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=baishuwei@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.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).