public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
Cc: Gregory Maxwell <greg@linuxpower.cx>,
	linux-kernel@vger.kernel.org, wakko@animx.eu.org
Subject: Re: Matrox Marvell G400
Date: Tue, 06 Feb 2001 09:36:59 +0000	[thread overview]
Message-ID: <21341.981452219@redhat.com> (raw)
In-Reply-To: <14A23BF37616@vcnet.vc.cvut.cz>
In-Reply-To: <14A23BF37616@vcnet.vc.cvut.cz>


VANDROVE@vc.cvut.cz said:
>  And if you insist on X, you can run first head through mga with
> usefbdev /dev/fb0 with hwcursor off, and secondary head through fbdev /
> dev/fb1. But it is not supported by me (and neither by XFree guys
> AFAIK, not even talking about Matrox support guys) - I support only
> first head in X and secondary head used for 'fbtv -k'.

Unless your machine is x86, and you use the binary-only HALlib from Matrox,
that is. :(

However, since the second heads of both G400 and G450 cards are supported 
in matroxfb, there's no real reason why the support in the 'real' XFree86 
driver should be so far behind. The main barrier to dual-head support in 
XFree86, last time I knew, was the lack of a way to _configure_ it. That's 
now been fixed, obviously. The HALlib is used only for mode setup, AFAICT. 
All acceleration is still done by the real driver. 

Petr - how much of the matroxfb code is yours to give, and would you permit
chunks of it to be reused under the XFree86 licence? Clean-room
reverse-engineering is such a PITA :)

> I'm trying... more or less. Next G450 BIOSes will have fix for
> matroxfb deadlock on boot, so there is at least some move. Although
> now when workaround is implemented in matroxfb, it is a bit late...

I think that workaround wants to be put in place for G400 too; not just 
G450.

--
dwmw2


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-02-06  9:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-05 19:04 Matrox Marvell G400 Petr Vandrovec
2001-02-06  9:36 ` David Woodhouse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-06 12:24 Petr Vandrovec
2001-02-05 16:31 Wakko Warner
2001-02-05 17:36 ` Gregory Maxwell
2001-02-06 18:06   ` Xavier Bestel
2001-02-05 18:54 ` Alan Olsen
2001-02-06  0:18   ` Ricky Beam

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=21341.981452219@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=greg@linuxpower.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wakko@animx.eu.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