From: Stephen Yee <stonepine@126.com>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: FYI: SM5xx toolchain project berliOS registration
Date: Thu, 23 Nov 2006 03:03:13 +0800 [thread overview]
Message-ID: <45649EF1.1050703@126.com> (raw)
In-Reply-To: <20061120214155.91777352643@atlas.denx.de>
Mr. Wolfgang,
After I ported your linuxppc_2_4_devel.git code to my system and
used the smi_disp_settings[2]("1024x768-60", 1024, 768, 15385,160, 24,
29, 3, 136, 6, 0 ) to replace the defualt 'fb.var' settings, the
Voyager GX PCI Demo Board Ver.A(a PCI cards with SiliconMotion SM501
chip) could work perfectly on PPC 405ep board to support dual CRT
monitors with 8bpp, Thanks all of the people in
linuxppc-embedded@ozlabs.org! and Thanks the Great code!
but,There is a small issue that when I used the 16bpp, the color is
not correct, I thinks it's the notorious RGB565 issue. I wanna get
the messages that the 16bpp have worked correctly on your "TQM5200"
board? and if YES, would you please give some advice to me about it?
Thanks and Best Regards,
Stephen Yee
Wolfgang Denk wrote:
>In message <4561F9F2.8020706@126.com> you wrote:
>
>
>>is Here a successful story about using SM501 on PPC platform with
>>this driver? and would you please give me some advices to drive this
>>devices?
>>
>>
>
>Not in the context of the 2.6 kernel. But we have a working
>configuration of MPC5200 + SM501 in our 2.4 kernel tree; see the
>"TQM5200" board config at
>http://www.denx.de/cgi-bin/gitweb.cgi?p=linuxppc_2_4_devel.git
>
>Best regards,
>
>Wolfgang Denk
>
>
>
next prev parent reply other threads:[~2006-11-22 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 14:36 FYI: SM5xx toolchain project berliOS registration Andrey Volkov
2006-11-20 18:54 ` Stephen Yee
2006-11-20 21:41 ` Wolfgang Denk
2006-11-22 19:03 ` Stephen Yee [this message]
2006-11-21 12:08 ` Andrey Volkov
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=45649EF1.1050703@126.com \
--to=stonepine@126.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wd@denx.de \
/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).