linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
Cc: <linuxppc-dev@lists.linuxppc.org>,
	<yellowdog-devel@lists.yellowdoglinux.com>
Subject: Re: radeonfb.c flakiness
Date: Sun, 17 Feb 2002 22:51:21 +0100	[thread overview]
Message-ID: <20020217215121.3523@smtp.wanadoo.fr> (raw)
In-Reply-To: <4BAF45B8-23D3-11D6-B713-0003938E434C@ivey.uwo.ca>


>Even with all of my changes, it seems the DFP screen will randomly stay
>blank under PPC Linux.
>
>Unfortunately, nothing I do can seem to bring it back to life (but all
>of the radeon debug info is absolutely fine).
>
>So some how we are not properly resetting the 7500 card or not properly
>initializing it.

Try removing the bit of code in my radeonfb.c that blast various
registers like MC_FB_LOCATION within a #ifdef CONFIG_ALL_PPC
in radeon_pci_register().

I suspect the sequence for changing those isn't good, the chip may
need some additional reset or delays.

>I can't understnad why the screen simply goes blank immediately after
>the kernel starts to boot.
>
>Ben, you mentioned something about playig with the memory mapping of the
>card.  I see code that does something along those lines in the
>radeonfb.c for screens that have dual heads.
>
>Do you have any ideas I should test to see if they impact the random
>startup blank screen issue (btw the kernel boots fine and I can blindly
>login and shutdown).  Changing VTs from 1 to 2 or 3 has no impact.
>
>Ideas welcome.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-02-17 21:51 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-13  1:08 new G4 dual 1 gig is here - how to install? Kevin B. Hendricks
2002-02-13  1:20 ` Tony 'Nicoya' Mantler
2002-02-13  1:55 ` Kevin B. Hendricks
2002-02-13  8:00   ` Olaf Hering
2002-02-13 13:49     ` Kevin B. Hendricks
2002-02-14  2:29   ` Kevin B. Hendricks
2002-02-14  3:53     ` Ani Joshi
2002-02-15 11:08       ` Kevin B. Hendricks
2002-02-16  9:30         ` Kevin B. Hendricks
2002-02-16 14:44           ` SMP kernel configuration question? Kevin B. Hendricks
2002-02-16 19:26             ` Benjamin Herrenschmidt
2002-02-16 15:39           ` SMP kernel seems to work fine Kevin B. Hendricks
2002-02-16 19:24           ` new G4 dual 1 gig is here - how to install? Benjamin Herrenschmidt
2002-02-14 13:53   ` Kevin B. Hendricks
2002-02-14 18:08     ` benh
2002-02-14 19:31       ` Christopher C. Chimelis
2002-02-13  2:25 ` Tom Rini
2002-02-13  5:37 ` Olaf Hering
2002-02-16  2:24 ` Kevin B. Hendricks
2002-02-16 19:19   ` Benjamin Herrenschmidt
2002-02-17 18:22     ` radeonfb.c flakiness Kevin B. Hendricks
2002-02-17 21:51       ` Benjamin Herrenschmidt [this message]
2002-02-18 20:55         ` Kevin B. Hendricks
2002-02-19  0:04           ` Benjamin Herrenschmidt
2002-02-16 23:59   ` question on best way to install other ide drives? Kevin B. Hendricks
2002-02-17  0:11     ` Tom Rini
2002-02-17 20:16     ` Timothy A. Seufert
2002-02-17 20:38       ` question: "disabling IRQ 54 defensively?" Kevin B. Hendricks
2002-02-17 21:53         ` Benjamin Herrenschmidt
2002-02-18  2:17         ` Final question: best wasy to move /, /usr, /home, etc? Kevin B. Hendricks
2002-02-18  2:36           ` Bastien Nocera
2002-02-18 16:16             ` Tom Rini
2002-02-18 16:20               ` Bastien Nocera
2002-02-18  3:12           ` Jeramy B. Smith
2002-02-18  8:42           ` Giuliano Pochini
2002-02-18 14:52             ` Derrik Pates
2002-02-18 15:05               ` Gabriel Paubert
2002-02-18 23:18                 ` Michael Heironimus
2002-02-18 17:31             ` David A. Gatwood
2002-02-17 21:52       ` question on best way to install other ide drives? Benjamin Herrenschmidt
2002-02-17 23:19         ` Tom Rini
2002-02-16  2:40 ` Weird bug problems with timing of NIC driver loading? Kevin B. Hendricks
2002-02-16 19:22   ` Benjamin Herrenschmidt

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=20020217215121.3523@smtp.wanadoo.fr \
    --to=benh@kernel.crashing.org \
    --cc=khendricks@ivey.uwo.ca \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=yellowdog-devel@lists.yellowdoglinux.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).