All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Alan Olsen <alan@clueserver.org>
Cc: Petr Vandrovec <VANDROVE@vc.cvut.cz>,
	Alex Deucher <adeucher@UU.NET>,
	linux-kernel@vger.kernel.org, jhartmann@valinux.com
Subject: Re: [OT] Re: 2.4.x, drm, g400 and pci_set_master
Date: Fri, 09 Feb 2001 11:19:39 +0000	[thread overview]
Message-ID: <4881.981717579@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10102081055350.9940-100000@clueserver.org>
In-Reply-To: <Pine.LNX.4.10.10102081055350.9940-100000@clueserver.org>


alan@clueserver.org said:
>  Both drivers want Matrox's HALlib. (Which is x86 binary only.) Matrox
> will not release the info on that interface to the chipset.  (Using
> the standard corporate excuse whenever they don't want to do something
> "Intelectual Property concerns".)

> Good luck on getting them to make an Alpha version of the library or
> get them to release the underlying library interface specs. 

I submitted a patch to XFree86 on Tuesday which drives the primary head of
G450. It's a cleaned up version of Matrox's own code, and it works on Alpha
for me. Dual head will come later - we have the example code in matroxfb to
work from. All the binary-only HALlib does is mode setup - all the
acceleration is done in the open source code anyway, even when the HALlib 
is present.

 ftp://ftp.uk.linux.org/pub/people/dwmw2/X/mga-G450-patch

--
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-09 11:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-08 19:30 [OT] Re: 2.4.x, drm, g400 and pci_set_master Petr Vandrovec
2001-02-08 18:41 ` Alex Deucher
2001-02-08 18:48   ` Jeff Hartmann
2001-02-09  4:56   ` Paul Jakma
2001-02-09  5:35     ` Paul Jakma
2001-02-08 19:05 ` Alan Olsen
2001-02-09 11:19   ` David Woodhouse [this message]
2001-02-09 13:24     ` Alan Cox
2001-02-09 13:28       ` David Woodhouse
2001-02-09 18:02         ` Alan Olsen

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=4881.981717579@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=adeucher@UU.NET \
    --cc=alan@clueserver.org \
    --cc=jhartmann@valinux.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.