From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: David Woodhouse <dwmw2@infradead.org>
Cc: <linux-kernel@vger.kernel.org>, marcel@mesa.nl
Subject: Re: Matrox G450 problems with 2.4.0 and xfree
Date: Wed, 31 Jan 2001 12:17:55 MET-1 [thread overview]
Message-ID: <142368953925@vcnet.vc.cvut.cz> (raw)
On 31 Jan 01 at 8:44, David Woodhouse wrote:
> On Tue, 30 Jan 2001, Marcel J.E. Mol wrote:
>
> > Installed a Matrox G450 on my linux system. Now it has problems
> > booting.
> >
> > Previously I had a matrox G400 card and that worked without any problems.
> >
> > Below follows .config for the 2.4.0 kernel.
> >
> > # CONFIG_FB_MATROX_G450 is not set
It is only for secondary head support - and all code which is guarded
by this define is executed after lockup occurs, so no, it is not the
reason why it works / does not work...
If it helped you, I think that rule (4) from my another posting
applies to you - you are just lucky...
I asked matrox devrel again, but no answer. And linking matroxfb with
512KB binary-only mgaHALlib.a is unacceptable personally for me, not
even talking about license issues... (and not talking about technical
problems with getting mgaHALlib to work in kernel environment...)
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
-
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/
next reply other threads:[~2001-01-31 11:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 12:17 Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-06 19:21 Matrox G450 problems with 2.4.0 and xfree Petr Vandrovec
2001-01-31 17:54 Petr Vandrovec
2001-02-06 18:16 ` Mike A. Harris
2001-01-31 17:41 J Brook
2001-01-31 0:30 Petr Vandrovec
2001-01-30 21:43 Marcel J.E. Mol
2001-01-30 21:53 ` tc lewis
2001-01-30 23:06 ` Marcel J.E. Mol
2001-01-31 8:44 ` David Woodhouse
2001-01-31 8:50 ` Marcel J.E. Mol
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=142368953925@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@mesa.nl \
/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