From: "Michel Dänzer" <michdaen@iiic.ethz.ch>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: R Shapiro <reshapiro@mediaone.net>, Olaf Hering <olh@suse.de>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: lcd17 kernel patches?
Date: Wed, 08 Aug 2001 02:49:05 +0200 [thread overview]
Message-ID: <3B708C81.DE87DDC2@iiic.ethz.ch> (raw)
In-Reply-To: Pine.LNX.4.05.10108070947420.5836-100000@callisto.of.borg
Geert Uytterhoeven wrote:
>
> On Mon, 6 Aug 2001, Michel Dänzer wrote:
> > R Shapiro wrote:
> > > Olaf Hering writes:
> > > > The correct fix is either "video=1280x1024-8@60" as kernel arg (that
> > > > may work)
> > >
> > > OK, I just had time to rebuild 2.4.8-pre3-ben0 with the patch undone.
> > > This video arg with that kernel doesn't solve the problem. I still
> > > get no video on boot.
> >
> > Wouldn't it have to be video=aty128fb:1280x1024-8@60 anyway, and is the
> > modedb
>
> video=mode specifies the global mode, for all fbdevs that use modedb.
Ah, cool. So what's your theory on why it didn't work for R?
> > even used on PPC yet?
>
> That's not the right question :-) Modedb doesn't depend on the architecture,
> but on the driver.
I meant to say 'in aty128fb on PPC'. Last time I looked, the call to find a
mode was disabled for PPC.
> Yes, atyfb was the first one to have modedb. Remember, I have a RAGE II+ in
> my LongTrail :-)
Didn't mean to question that.
> PowerMac/CHRP has even extra modedb support in macmodes.
Would that explain the disabled direct call?
--
Earthling Michel Dänzer (MrCooper) \ Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast \ XFree86 and DRI project member
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-08-08 0:49 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
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 [this message]
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=3B708C81.DE87DDC2@iiic.ethz.ch \
--to=michdaen@iiic.ethz.ch \
--cc=daenzer@debian.org \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=olh@suse.de \
--cc=reshapiro@mediaone.net \
/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).