linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Robert E Brose II <bob@kunk.jriver.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: controlfb and X
Date: Sun, 5 Nov 2000 21:27:50 -0600 (CST)	[thread overview]
Message-ID: <20001106032750.5523.qmail@kunk.jriver.com> (raw)


I've been doing some testing of the controlfb driver in the
2.2.17 tree as well as the 2.4.0-test10 paulus tree.

The problem is that the controlfb driver doesn't recognize more than
2 megs of vram. This particular Mac 7500 has 4 megs installed which
works perfectly in MacOS.

With 2.2.18pre18, 2 megs only is available. Running XFree86-3.3.6-11.2
on the Mac 7500 will do 800x600 in 24 bits as expected and 1024x768 in
16 bits but not 1024x768 in 24 bits (not enough ram).

With 2.4.0-test10 (which includes dma and parameter line changes in
controlfb) forcing the video ram to 4 megs works fine for console
modes (for example vmode 17 32) HOWEVER when the XF86_FBdev server
is run it locks up the machine with a black screen of death. (not
pingable, keyboard is dead, etc).
Also, building my own Xfree 4.01 server results in the same black
screen of death.
OTOH Xpmac rev 10 works fine (but doesn't support serial mice AFAIK).

I'm assuming the problem is in the dma code added to controlfb.c in the
2.4.x version. Has anyone run into this or had different results?

Bob
--
Robert E. Brose II    N0QBJ
http://www.jriver.com/~bob/
bob@kunk.jriver.com

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

             reply	other threads:[~2000-11-06  3:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-06  3:27 Robert E Brose II [this message]
2000-11-06 22:44 ` controlfb and X Michel Lanners
2000-11-07  6:16   ` bob
2000-11-07  7:05   ` Brad Boyer
2000-11-07 17:59     ` bob
2000-11-07 19:47     ` Michel Lanners
2000-11-07 21:22       ` bob
2000-11-18 18:31         ` controlfb and X (fixed) Michel Lanners
2000-11-09  6:50 ` controlfb and X Michel Lanners

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=20001106032750.5523.qmail@kunk.jriver.com \
    --to=bob@kunk.jriver.com \
    --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).