All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: "Z. Liu" <liuzx@knownsec.com>, Helge Deller <deller@gmx.de>,
	linux-fbdev@vger.kernel.org, it+linux-fbdev@molgen.mpg.de
Subject: Re: Why is mgag200 not used over matroxfb?
Date: Tue, 3 Jan 2023 17:20:06 +0100	[thread overview]
Message-ID: <c11a7128-ec34-c497-e012-577a4928dc94@molgen.mpg.de> (raw)
In-Reply-To: <7b85b832-e6fd-fe42-c6a1-93ebb591383c@molgen.mpg.de>

Dear Thomas,


I have to correct myself.


Am 16.12.22 um 14:16 schrieb Paul Menzel:

> Am 16.12.22 um 13:27 schrieb Thomas Zimmermann:
> 
>> Am 15.12.22 um 17:39 schrieb Paul Menzel:
> 
> […]
> 
>>> Between Linux 5.10.103 and 5.10.110/5.15.77, matrixfb fails to load.
>>
>> Off-topic, but related. matroxfb is obsolete and there's a maintained 
>> DRM replacement (mgag200) for this hardware.
> 
> I also remembered something like this in the back of my head. Though I 
> thought about using simpledrm (`DRM_SIMPLEDRM`), we do not build though.
> 
>> Is there anything missing from mgag200 that prevents you from switching?
> No, it looks like the matroxfb modules take precedence over the mgag200 
> module:
> 
>      $ grep -e FB_MATROX -e MGAG /boot/config-5.15.77.mx64.440
>      CONFIG_DRM_MGAG200=m
>      CONFIG_FB_MATROX=m
>      CONFIG_FB_MATROX_MILLENIUM=y
>      CONFIG_FB_MATROX_MYSTIQUE=y
>      CONFIG_FB_MATROX_G=y
>      CONFIG_FB_MATROX_I2C=m
>      # CONFIG_FB_MATROX_MAVEN is not set
> 
>      $ lsmod | grep matrox
>      matroxfb_base          28672  0
>      matroxfb_g450          16384  1 matroxfb_base
>      matroxfb_Ti3026        16384  1 matroxfb_base
>      matroxfb_accel         16384  1 matroxfb_base
>      matroxfb_DAC1064       20480  1 matroxfb_base
>      g450_pll               16384  2 matroxfb_g450,matroxfb_DAC1064
>      matroxfb_misc          20480  5 g450_pll,matroxfb_Ti3026,matroxfb_base,matroxfb_g450,matroxfb_DAC1064

The search string was incorrect. The module mgag200, is loaded:

     $ lsmod | grep mgag200
     mgag200                36864  0
     drm_kms_helper        241664  3 mgag200
     drm                   524288  3 drm_kms_helper,mgag200
     i2c_algo_bit           16384  1 mgag200

and it is used according to `lspci`:

     $ lspci -nn -k -s 09:03.
     09:03.0 VGA compatible controller [0300]: Matrox Electronics 
Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a)
         DeviceName: Embedded Video
         Subsystem: Dell MGA G200eW WPCM450 [1028:02d3]
         Kernel driver in use: mgag200
         Kernel modules: matroxfb_base, mgag200

So, it was only a cosmetic issue.


Kind regards,

Paul

  reply	other threads:[~2023-01-03 16:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 16:39 matroxfb: cannot determine memory size Paul Menzel
2022-12-15 23:02 ` Helge Deller
2022-12-16 11:58   ` Paul Menzel
2022-12-16 21:21     ` Helge Deller
2022-12-19 11:58       ` Paul Menzel
2022-12-19 12:19         ` Helge Deller
2023-02-16 12:50     ` Linux regression tracking #update (Thorsten Leemhuis)
2022-12-16 12:27 ` Thomas Zimmermann
2022-12-16 13:16   ` Why is mgag200 not used over matroxfb? (was: matroxfb: cannot determine memory size) Paul Menzel
2023-01-03 16:20     ` Paul Menzel [this message]
2023-01-04  8:19       ` Why is mgag200 not used over matroxfb? Thomas Zimmermann

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=c11a7128-ec34-c497-e012-577a4928dc94@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=deller@gmx.de \
    --cc=it+linux-fbdev@molgen.mpg.de \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=liuzx@knownsec.com \
    --cc=tzimmermann@suse.de \
    /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.