From: R Shapiro <reshapiro@mediaone.net>
To: Olaf Hering <olh@suse.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: lcd17 kernel patches?
Date: Sun, 5 Aug 2001 15:57:28 -0400 [thread overview]
Message-ID: <15213.42280.789880.989118@mediaone.net> (raw)
In-Reply-To: <20010805200639.A14938@suse.de>
Olaf Hering writes:
> Try this one in the meantime:
OK, this mostly works with the 2.4.7 kernel sources, but there's one
important difference between the building a kernel this way and
running that prebuilt 2.4.2. The prebuilt kernel has working video
immediately on booting. The kernel I built with your patch has no
video at all until I run 'fbset 1280x1024-60'. Clearly there's more
to that prebuilt 2.4.2 than just an additional mode definition.
But this will do for now - thanks for the patch. I created an init.d
entry which runs the fbset command and I set it to run very early
(00). So at least I can see some of the boot messages as they go by.
Maybe I could put it in inittab or rc.sysinit to get it even earlier.
But I might rather wait for a real patch.
--
reshapiro@mediaone.net
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-08-05 19:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15213.15313.170106.433877@mediaone.net>
[not found] ` <20010805200639.A14938@suse.de>
2001-08-05 19:06 ` lcd17 kernel patches? R Shapiro
2001-08-05 19:57 ` R Shapiro [this message]
2001-08-05 23:16 ` Olaf Hering
2001-08-06 7:34 ` Geert Uytterhoeven
2001-08-06 8:06 ` Olaf Hering
2001-08-06 10:59 ` R Shapiro
2001-08-06 11:05 ` Olaf Hering
2001-08-06 11:42 ` R Shapiro
2001-08-06 12:19 ` Michel Dänzer
2001-08-07 0:17 ` R Shapiro
2001-08-07 7:16 ` Michel Dänzer
2001-08-07 7:49 ` Geert Uytterhoeven
2001-08-07 9:00 ` Olaf Hering
2001-08-08 0:49 ` Michel Dänzer
2001-08-08 6:59 ` Geert Uytterhoeven
2001-08-08 11:25 ` R Shapiro
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=15213.42280.789880.989118@mediaone.net \
--to=reshapiro@mediaone.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=olh@suse.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).