From: Benjamin Herrenschmidt <bh40@calva.net>
To: Takashi Oe <toe@unlserve.unl.edu>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.4.0-test3
Date: Tue, 11 Jul 2000 00:14:10 +0200 [thread overview]
Message-ID: <20000710221410.2067@192.168.1.10> (raw)
In-Reply-To: <Pine.LNX.3.96LJ1.1b7.1000710164335.14195C-100000@ofey.inetnebr.com>
>
>Why is pmac_backlight.c compiled in for CONFIG_ALL_PPC? Isn't it
>PowerBook only thing?
Well, if you change that, then chipsfb.c, atyfb.c, aty128fb.c and via-
pmu.c must be changed too. It's not completely powerbook only since, at
term, this could driver also external LVDS LCD backlight.
>> Well, you can check disabling that (and the call that sets up this BAT in
>> head.S) but don't forget, if you do that, to also declare
>> bootx_text_mapped to 0 before leaving prom.c
>
>601's BAT doesn't have G bit. Maybe that's the problem?
Maybe. I'll push a change without it and see
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-10 22:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-10 11:56 2.4.0-test3 Iain Sandoe
2000-07-10 12:10 ` 2.4.0-test3 Benjamin Herrenschmidt
2000-07-10 15:07 ` 2.4.0-test3 Andreas Tobler
2000-07-10 16:05 ` 2.4.0-test3 Benjamin Herrenschmidt
2000-07-10 18:30 ` 2.4.0-test3 Andreas Tobler
2000-07-10 21:48 ` 2.4.0-test3 Takashi Oe
2000-07-10 22:14 ` Benjamin Herrenschmidt [this message]
2000-07-10 22:20 ` 2.4.0-test3 Takashi Oe
2000-07-10 22:26 ` 2.4.0-test3 Andreas Tobler
2000-07-11 7:58 ` 2.4.0-test3 Gabriel Paubert
2000-07-11 8:45 ` 2.4.0-test3 Benjamin Herrenschmidt
2000-07-11 10:12 ` 2.4.0-test3 Gabriel Paubert
2000-07-11 10:41 ` 2.4.0-test3 Benjamin Herrenschmidt
2000-07-11 12:38 ` 2.4.0-test3 Gabriel Paubert
2000-07-11 15:57 ` 2.4.0-test3 Benjamin Herrenschmidt
2000-07-11 11:52 ` 2.4.0-test3 Takashi Oe
-- strict thread matches above, loose matches on Subject: below --
2000-07-10 16:12 2.4.0-test3 Iain Sandoe
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=20000710221410.2067@192.168.1.10 \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=toe@unlserve.unl.edu \
/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).