mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Chris Rankin <rankincj@gmail.com>, daniel@ffwll.ch
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Removal of mga driver from Linux 6.3
Date: Mon, 23 Jan 2023 10:07:17 +0100	[thread overview]
Message-ID: <e0637ab4-5165-6aa9-e85c-7b451db4c598@suse.de> (raw)
In-Reply-To: <CAK2bqVK1s2BLcR+HOnTn=i9s60GsREnVXWz2T9uUjYfQawUH9w@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1135 bytes --]

Hi

Am 21.01.23 um 23:28 schrieb Chris Rankin:
> Hi,
> 
> With reference to the recent deletion of the mga driver from Linux 6.3:
> 
> I actually own an old machine that still contains a Matrox Millenium II 
> graphics card. This machine has not run X for several yonks, and so the 
> loss of DRM support doesn't concern me.
> 
> What would concern me would be losing the graphics frame buffer device 
> (matroxfb), because a VGA console is just too small;

No worries. The matroxfb driver is still there and will remain. Even 
Xorg should work in principle.

What has been removed is the kernel side for 3d support. But this has 
been non-functional anyway, as the rsp code in Mesa had been removed 
long ago.

Best regards
Thomas

> 
> CONFIG_FB_MATROX=y
> CONFIG_FB_MATROX_MILLENIUM=y
> # CONFIG_FB_MATROX_MYSTIQUE is not set
> # CONFIG_FB_MATROX_G is not set
> CONFIG_FB_MATROX_I2C=y
> 
> Cheers,
> Chris
> 

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

           reply	other threads:[~2023-01-23  9:07 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAK2bqVK1s2BLcR+HOnTn=i9s60GsREnVXWz2T9uUjYfQawUH9w@mail.gmail.com>]

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=e0637ab4-5165-6aa9-e85c-7b451db4c598@suse.de \
    --to=tzimmermann@suse.de \
    --cc=daniel@ffwll.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rankincj@gmail.com \
    /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

all inboxes | Powered by JetHome®