linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: drow@false.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: controlfb: please test!
Date: Sun, 19 Mar 2000 09:30:55 +0100 (CET)	[thread overview]
Message-ID: <200003190830.JAA00344@piglet.grunz.lu> (raw)
In-Reply-To: <20000318143259.A11235@drow.res.cmu.edu>


Hi Dan,

On  18 Mar, this message from Daniel Jacobowitz echoed through cyberspace:
> Well, first of all, there are two different 'current' controlfb's.  One
> of them is in the PPC 2.2 tree and the other in the 2.3 tree (both
> bitkeeper), I believe.  Did you try both of those?  I'm pretty sure I
> fixed this quite thoroughly in one or the other.

2.2 works well for me, but doesn't seem to work for Andrew Fyfe,
according to the comments in 2.3. 2.2 detects my 4M, 2.3 doesn't.

> Actually, on closer look, I thought that the 2.3 code was correct.
> Could you compare to Andrew's observations in the comment above the
> code?  Is he wrong?  I certainly can't see how his comment would be
> unless there is a memory scheme he was not detecting, and I do not
> think there is.

At least his code and comments are not _entirely_ correct for my
machine. Here's what I've found so far:

- control manages mem in chunks of 2M (a pair of DIMMs), within a
region of 8M in size.
- 2M in bank 1, and 4M, are accessed at offset 0x0.
- 2M in bank 2 are accessed at offset 6M.
- the 2.3 code doesn't detect the mem at 2M in my case. It seems
writing to 0x0 garbles the memory contents at 2M: write to
2M, write to 0x0-garbling 2M, detect 0x0, detect 2M-garbled, so nothing
detected.

> I have a bunch of other patches to merge for controlfb anyway, so now
> is a good time to straighten this out... with luck and speed we can get
> a fix into 2.3.99preX.

I'll speed up then ;-)

The next step is to compile a better detection check, that can detect
mirrored memory regions, so that I can find out what's wrong between
0x0 and 2M..... It's actually very strange, as my 4M do work when
accessed in one block starting at 0x0... so 2M would have to be
different from 0x0 ???

By the way, somewhere I have an alternate OF driver for control, that
IIRC came out of darwin, and it ver accesses VRAM only at 0x0 or 6M....
Unfortunately, it's too big to fit into nvramrc ;-))

Cheers

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-03-19  8:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-18  9:03 controlfb: please test! Michel Lanners
2000-03-18 19:32 ` Daniel Jacobowitz
2000-03-19  8:30   ` Michel Lanners [this message]
2000-03-19  8:46     ` Daniel Jacobowitz
2000-03-19 11:41       ` Michel Lanners
2000-03-19 18:24         ` Michel Lanners
2000-03-19 21:53           ` Michael R. Zucca

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=200003190830.JAA00344@piglet.grunz.lu \
    --to=mlan@cpu.lu \
    --cc=drow@false.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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).