linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: geert@linux-m68k.org
Cc: toe@unlserve.unl.edu, linuxppc-dev@lists.linuxppc.org
Subject: Re: [patch] VRAM detection in controlfb
Date: Mon, 5 Jun 2000 08:01:29 +0200 (CEST)	[thread overview]
Message-ID: <200006050601.IAA01779@piglet.grunz.lu> (raw)
In-Reply-To: <Pine.LNX.4.05.10006030855010.1278-100000@callisto.of.borg>


Hi there,

On   3 Jun, this message from Geert Uytterhoeven echoed through cyberspace:
> Immediately after I read this, I thought: isn't that already implemented
> through fbmem.c? Then I remembered that controlfb is initialized from offb, and
> not directly from fbmem_init().
>
> I looked at the source, and surprise, controlfb can also be initialised on its
> own:
(patch deleted)

I applied the patch; XF4 works (just as badly) as before, but Xpmac
crashes big-time (panic on access of bad area (9C9C9D9D, iirc). makes
syslogd panic as well ??). But it started misbehaving already before
your patch, so there is probably something else as well...

I'll keep on looking.

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


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

  reply	other threads:[~2000-06-05  6:01 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-31 22:43 [patch] VRAM detection in controlfb Michel Lanners
2000-06-01  0:57 ` Takashi Oe
2000-06-03  6:28   ` Michel Lanners
2000-06-03  7:13     ` Takashi Oe
2000-06-03  7:30       ` Geert Uytterhoeven
2000-06-03  8:49         ` Michel Dänzer
2000-06-03  9:22           ` Geert Uytterhoeven
2000-06-06 19:25             ` Michael Schmitz
2000-06-06 21:52               ` Michel Lanners
2000-06-03  7:38     ` Geert Uytterhoeven
2000-06-05  6:01       ` Michel Lanners [this message]
2000-06-04  0:09     ` Daniel Jacobowitz
2000-06-04  0:31       ` Ani Joshi
2000-06-04 13:55         ` Michel Lanners
2000-06-05 12:59           ` Michel Dänzer
2000-06-03  9:16 ` Franz Sirl
2000-06-04  7:09   ` Michel Lanners
2000-06-04 15:08     ` Tony Mantler
2000-06-04 17:48       ` Daniel Jacobowitz
2000-06-05  5:48         ` Michel Lanners
2000-06-05 12:40           ` Tony Mantler
2000-06-05 13:51             ` Michel Lanners
2000-06-05 14:15               ` Geert Uytterhoeven
2000-06-05 23:49                 ` Tony Mantler
2000-06-06  5:15                 ` Timothy A. Seufert
2000-06-06 19:49             ` Michael Schmitz
2000-06-06 21:58               ` Michel Lanners
2000-06-07  7:59                 ` Geert Uytterhoeven
     [not found] <20000607233456Z.roikawa@rr.iij4u.or.jp>
2000-06-07 15:10 ` Geert Uytterhoeven
2000-06-07 15:20   ` Michael Schmitz
2000-06-07 15:41     ` Geert Uytterhoeven
2000-06-07 15:58   ` Ryuichi Oikawa
2000-06-07 19:11     ` Geert Uytterhoeven

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=200006050601.IAA01779@piglet.grunz.lu \
    --to=mlan@cpu.lu \
    --cc=geert@linux-m68k.org \
    --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).