From: Wolfgang Denk <wd@denx.de>
To: Stefan Nickl <Stefan.Nickl@kontron.com>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Lite5200 PCI not working
Date: Thu, 08 Jul 2004 14:12:55 +0200 [thread overview]
Message-ID: <20040708121300.75EA7C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 08 Jul 2004 13:57:17 +0200." <1089287836.6000.46.camel@lucy.pep-kaufbeuren.de>
Dear Stefan,
in message <1089287836.6000.46.camel@lucy.pep-kaufbeuren.de> you wrote:
>
> I now found out why my picture looked so dim...
> My trusty old CRT was finally broken. ARG!
:-(
> Ok, but the picture from the console (penguin, messages ...)
> is still very blue-ish; however X is perfectly ok with
> the accelerated driver, so with the above said by you,
> it this what I have to expect?
No, colors should be fine on the console, too. Are you sure you are
using the latest kernel drivers? Note that there are both kernel
modifications plus the X11 driver.
> I understand that console messages on the VGA are not
> important for an embedded system when the apps (can)
> work correctly.
They are important in may cases, and they should be OK. At least this
is working fine here.
There is a Linux kernel image on our FTP server which you could give
a try:
ftp://adm:PASSWORD@www.denx.de/ftp/pub/fujitsu/Coral-P/uImage-LITE5200
> Btw: "fbset -depth 24" and bootargs+="video=mb86290:1024x768-24@70"
> apparently have no effect at all...
Ummm.. I will check this...
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
If A equals success, then the formula is A = X + Y + Z. X is work. Y
is play. Z is keep your mouth shut. - Albert Einstein
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-08 12:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 9:18 Lite5200 PCI not working Wolfgang Denk
2004-07-01 11:36 ` Kate Alhola
2004-07-01 12:38 ` Stefan Nickl
2004-07-01 22:20 ` Kate Alhola
2004-07-01 22:29 ` Wolfgang Denk
2004-07-02 4:43 ` Kate Alhola
2004-07-02 7:22 ` Wolfgang Denk
2004-07-02 7:55 ` Kate Alhola
2004-07-02 8:51 ` Wolfgang Denk
2004-07-02 11:35 ` Lite5200 CoralP issues Kate Alhola
2004-07-02 13:46 ` Mark Chambers
2004-07-02 14:51 ` Wolfgang Denk
2004-07-08 11:57 ` Lite5200 PCI not working Stefan Nickl
2004-07-08 12:12 ` Wolfgang Denk [this message]
[not found] <20040708124140.E18E4C109F@atlas.denx.de>
2004-07-08 13:34 ` Stefan Nickl
-- strict thread matches above, loose matches on Subject: below --
2004-06-21 11:12 Iñigo Lopez Barranco
2004-06-21 11:48 ` Gerhard Jaeger
2004-06-21 10:03 Iñigo Lopez Barranco
2004-06-21 10:26 ` Gerhard Jaeger
2004-06-21 10:53 ` Wolfgang Denk
2004-06-21 11:39 ` Gerhard Jaeger
2004-06-21 14:12 ` Kate Alhola
2004-06-21 15:14 ` Wolfgang Denk
2004-06-21 16:20 ` Kate Alhola
2004-07-01 8:41 ` Stefan Nickl
2004-07-01 8:52 ` Wolfgang Denk
2004-06-21 10:51 ` Wolfgang Denk
2004-06-21 19:19 ` Mark Jonas
2004-06-22 6:08 ` Gerhard Jaeger
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=20040708121300.75EA7C109F@atlas.denx.de \
--to=wd@denx.de \
--cc=Stefan.Nickl@kontron.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).