LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: rene@exactco.de, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Trevor Dickinson <rtd2@xtra.co.nz>,
	hypexed@yahoo.com.au, mad skateman <madskateman@gmail.com>,
	Christian Zigotzky <info@xenosoft.de>
Subject: Re: drm/mgag200: Fix big-endian support
Date: Thu, 27 Aug 2026 18:38:59 +0200	[thread overview]
Message-ID: <8ff12e31-2677-c554-cc3d-1bade8138876@xenosoft.de> (raw)
In-Reply-To: <4ba35195-5421-4c52-bbe5-ed88e15e394d@suse.de>

On 27/08/26 08:36, Thomas Zimmermann wrote:
> Hi
>
> Am 26.08.26 um 19:30 schrieb Christian Zigotzky:
>> On 26 August 2026 at 05:23 pm, Thomas Zimmermann 
>> <tzimmermann@suse.de> wrote:
>>
>> Hi
>>
>> Could be that we have to enable access to the ROM first. That's why 
>> it returns only 0xffff. Does the card display output when you switch 
>> on the computer?
>>
>> Best regards
>> Thomas
>>
>> - - -
>>
>> Hello Thomas,
>>
>> No, the card doesn’t display output when I switch on the computer.
>
> Attached you'll find another patch that also enables ROM access in the 
> PCI config options.  I took the code out of the old matroxfb driver 
> without further testing. Please try and report back on the results.
>
> Best regards
> Thomas
>

Hello Thomas,

Thank you for your effort to solve the problem. Unfortunately, your new 
patch doesn't solve the problem either. The error outputs are the same 
as before.

Cheers,
Christian

-- 
Sent with BrassMonkey 34.3.2.1 (https://github.com/chzigotzky/Web-Browsers-and-Suites-for-Linux-PPC/releases/tag/BrassMonkey_34.3.2.1)



  reply	other threads:[~2026-08-27 16:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-02 18:06 drm/mgag200: Fix big-endian support Christian Zigotzky
2026-08-26  7:17 ` Christian Zigotzky
2026-08-26  7:48 ` Thomas Zimmermann
2026-08-26  9:06 ` Thomas Zimmermann
2026-08-26 15:07   ` Christian Zigotzky
2026-08-26 15:22     ` Thomas Zimmermann
2026-08-26 17:30       ` Christian Zigotzky
2026-08-27  6:36         ` Thomas Zimmermann
2026-08-27 16:38           ` Christian Zigotzky [this message]
2026-08-28  5:57             ` Thomas Zimmermann
2026-08-28 10:19               ` Christian Zigotzky
2026-08-31  8:20                 ` 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=8ff12e31-2677-c554-cc3d-1bade8138876@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=hypexed@yahoo.com.au \
    --cc=info@xenosoft.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=madskateman@gmail.com \
    --cc=rene@exactco.de \
    --cc=rtd2@xtra.co.nz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox