From: Song Sam <samlinuxppc@yahoo.com.cn>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Could 2_4_devel support RPXlite DW LCD panel?
Date: Mon, 26 Jul 2004 10:29:43 +0800 (CST) [thread overview]
Message-ID: <20040726022943.71278.qmail@web15206.mail.bjs.yahoo.com> (raw)
In-Reply-To: <22313616.1090788110569.JavaMail.root@wamui02.slb.atl.earthlink.net>
--- "Robert P. J. Day" <rpjday@mindspring.com> wrote:
> > I want to port 2_4_devel on RPXlite DW with framebuffer support and
> > tried linuxppc_2_4_devel in linuxppc official BK tree and DENX tree
> > repectively but failed.Could anyone try it before?> > Worked?
>
> is it just the FB selection that's causing problems? and what do you
> mean by "failed"? you'll have to be more specific. does the system
> fail to boot? does it boot but the FB doesn't work? etc, etc.
Sorry,I neglected some points here.Firstly,I could
make the 2_4_devel work on RPXlite DW board with
rpxlite_defconfig.Then when I added FB configuration
to build these two kernel tree,both could boot right
with "console=ttyS0,9600" but hanged after kernel
uncompressed with "console=tty0".There were no display
on LCD panel.Yeah,2.4.18 kernel can work right on
RPXlite DW board with FB and USB HOST mode
support.Also the LCD panel is NL6448BC20-08.
Thanks.
Sam
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-26 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-25 20:41 Could 2_4_devel support RPXlite DW LCD panel? Robert P. J. Day
2004-07-26 2:29 ` Song Sam [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-23 17:22 random ramblings on 8xx patches (long and tedious :-) Wolfgang Denk
2004-07-25 3:00 ` Could 2_4_devel support RPXlite DW LCD panel? Song Sam
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=20040726022943.71278.qmail@web15206.mail.bjs.yahoo.com \
--to=samlinuxppc@yahoo.com.cn \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rpjday@mindspring.com \
/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).