From: Helge Deller <deller@gmx.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>, "Z. Liu" <liuzx@knownsec.com>
Cc: it+linux-fbdev@molgen.mpg.de, Rich Felker <dalias@libc.org>,
stable@vger.kernel.org, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] matroxfb: G200eW: Increase max memory from 1 MB to 16 MB
Date: Mon, 2 Jan 2023 15:48:21 +0100 [thread overview]
Message-ID: <17a2982e-f4e8-f8bd-db8f-dd14bf27b4e7@gmx.de> (raw)
In-Reply-To: <20230102135731.6487-1-pmenzel@molgen.mpg.de>
On 1/2/23 14:57, Paul Menzel wrote:
> Commit 62d89a7d49af ("video: fbdev: matroxfb: set maxvram of vbG200eW to
> the same as vbG200 to avoid black screen") accidently decreases the
> maximum memory size for the Matrox G200eW (102b:0532) from 8 MB to 1 MB
> by missing one zero. This caused the driver initialization to fail with
> the messages below, as the minimum required VRAM size is 2 MB:
>
> [ 9.436420] matroxfb: Matrox MGA-G200eW (PCI) detected
> [ 9.444502] matroxfb: cannot determine memory size
> [ 9.449316] matroxfb: probe of 0000:0a:03.0 failed with error -1
>
> So, add the missing 0 to make it the intended 16 MB. Successfully tested on
> the Dell PowerEdge R910/0KYD3D, BIOS 2.10.0 08/29/2013, that the warning is
> gone.
>
> While at it, add a leading 0 to the maxdisplayable entry, so it’s aligned
> properly. The value could probably also be increased from 8 MB to 16 MB, as
> the G200 uses the same values, but I have not checked any datasheet.
>
> Note, matroxfb is obsolete and superseded by the maintained DRM driver
> mga200, which is used by default on most systems where both drivers are
> available. Therefore, on most systems it was only a cosmetic issue.
>
> Fixes: 62d89a7d49af ("video: fbdev: matroxfb: set maxvram of vbG200eW to the same as vbG200 to avoid black screen")
> Link: https://lore.kernel.org/linux-fbdev/972999d3-b75d-5680-fcef-6e6905c52ac5@suse.de/T/#mb6953a9995ebd18acc8552f99d6db39787aec775
> Cc: it+linux-fbdev@molgen.mpg.de
> Cc: Z. Liu <liuzx@knownsec.com>
> Cc: Rich Felker <dalias@libc.org>
> Cc: stable@vger.kernel.org
> Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de>
applied this v1 version to the fbdev git tree.
Thanks!
Helge
> ---
> drivers/video/fbdev/matrox/matroxfb_base.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/video/fbdev/matrox/matroxfb_base.c b/drivers/video/fbdev/matrox/matroxfb_base.c
> index 0d3cee7ae7268..a043a737ea9f7 100644
> --- a/drivers/video/fbdev/matrox/matroxfb_base.c
> +++ b/drivers/video/fbdev/matrox/matroxfb_base.c
> @@ -1378,8 +1378,8 @@ static struct video_board vbG200 = {
> .lowlevel = &matrox_G100
> };
> static struct video_board vbG200eW = {
> - .maxvram = 0x100000,
> - .maxdisplayable = 0x800000,
> + .maxvram = 0x1000000,
> + .maxdisplayable = 0x0800000,
> .accelID = FB_ACCEL_MATROX_MGAG200,
> .lowlevel = &matrox_G100
> };
prev parent reply other threads:[~2023-01-02 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 13:57 [PATCH] matroxfb: G200eW: Increase max memory from 1 MB to 16 MB Paul Menzel
2023-01-02 14:48 ` Helge Deller [this message]
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=17a2982e-f4e8-f8bd-db8f-dd14bf27b4e7@gmx.de \
--to=deller@gmx.de \
--cc=dalias@libc.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=it+linux-fbdev@molgen.mpg.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuzx@knownsec.com \
--cc=pmenzel@molgen.mpg.de \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).