linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: O.Waller@ee.qub.ac.uk
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: matroxfb, anybody?
Date: Thu, 17 Dec 1998 22:46:30 +0100 (CET)	[thread overview]
Message-ID: <199812172146.WAA00356@piglet.cpu.lu> (raw)
In-Reply-To: <Pine.SGI.4.02A.9812151054230.11112-100000@myst.ee.qub.ac.uk>


On  15 Dec, this message from Owen Waller echoed through cyberspace:
> On Sun, 13 Dec 1998, Michel Lanners wrote:
> 
>> Anybody successfull in running matroxfb with recent vger kernels?
> 
> I've got it running on version 2.1.127 - I haven't tried on anything more
> recent. What kernel version are you running.

2.1.130. What I hate most is it doesn't complete the PCI scan
routine.... maybe a simple bug very early in the init code?

....
>> aborts (slightly older matroxfb.c (1.6c)) or hangs the system (most
>> recent matroxfb.c (1.8)).
> 
> Pass, have you asked Petr (Petr Vandrovec <VANDROVE@vc.cvut.cz>) about
> this. I've been testing Petr's driver on a Mystique and haven't seen
> anything like this.

Not yet...

>> I've also tried to compile-in matroxfb without controlfb, but that
>> failed because offb.c wasn't in (undefined ref to console_getmode et
> 
> Generally I've compiled in matroxfb, controlfb and offb into the kernel
> which compile and run without any problems. I haven't tried leaving
> controlfb out.

This is exactly what I need... I'd like to use matrox alongside control
(have my TV on a second monitor ;-)

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
9, Montee St. Crepin           |    Ask Questions.  Make Mistakes.
L-1365 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

  reply	other threads:[~1998-12-17 21:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-13 10:40 matroxfb, anybody? Michel Lanners
1998-12-15 12:00 ` Owen Waller
1998-12-17 21:46   ` Michel Lanners [this message]
1999-01-30 10:00     ` dhiltgen@toocool.calpoly.edu
1999-01-30 12:09       ` Matt McLean
1999-01-30 15:32       ` Owen Waller
1999-01-30 23:34         ` matroxfb, anybody? (More details...) dhiltgen@toocool.calpoly.edu
1999-01-31  9:38           ` Gerd Knorr
1999-01-31 14:24             ` Geert Uytterhoeven
1999-02-06 15:22               ` Gerd Knorr
1999-01-31 14:36           ` Geert Uytterhoeven
1998-12-16  4:42 ` matroxfb, anybody? Troy Benjegerdes

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=199812172146.WAA00356@piglet.cpu.lu \
    --to=mlan@cpu.lu \
    --cc=O.Waller@ee.qub.ac.uk \
    --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).