From: Alex Deucher <alexdeucher@gmail.com>
To: Christian Zigotzky <chzigotzky@xenosoft.de>,
Wu Hoi Pok <wuhoipok@gmail.com>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>,
Alex Deucher <alexander.deucher@amd.com>,
developers DRI <dri-devel@lists.freedesktop.org>,
mad skateman <madskateman@gmail.com>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
Darren Stevens <darren@stevens-zone.net>,
hypexed@yahoo.com.au,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Christian Zigotzky <info@xenosoft.de>
Subject: Re: FSL P5040 board doesn't boot after DRM updates (drm-next-2024-09-19)
Date: Mon, 30 Sep 2024 09:26:59 -0400 [thread overview]
Message-ID: <CADnq5_PB8zUfCN-NcNpgHqzAv8A55o2hsYHAdnSBhEy525NLfA@mail.gmail.com> (raw)
In-Reply-To: <37D93804-DC55-4B2D-A82F-85BD45D9E131@xenosoft.de>
+ Wu Hoi Pok
This is likely related to the drm device rework.
Alex
On Sun, Sep 29, 2024 at 11:33 AM Christian Zigotzky
<chzigotzky@xenosoft.de> wrote:
>
> Hello,
>
> I tested the latest Git kernel with my VAPOR-X Radeon HD5870 1GB GDDR5 PCI-E DUAL DVI-I/HDMI/DP on my PASEMI Nemo board today.
> Unfortunately it has the same issue like my FSL P5040 board.
>
> I think it depends on which graphics card is used.
>
> It could be, that FSL P5020 boards are also affected.
>
> dmesg (via null modem RS-232 serial cable): https://www.xenosoft.de/PuTTY_P5040_U-Boot.log
>
> Please check the drm-next-2024-09-19 updates: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de848da12f752170c2ebe114804a985314fd5a6a
>
> Thanks,
> Christian
next prev parent reply other threads:[~2024-09-30 13:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADnq5_MM6UYOwFSPkZRauAyckFaUjCRGT97cVhsK=xZ9CzuXVw@mail.gmail.com>
[not found] ` <20EA4BE5-B349-4406-89EA-3D442717EC03@xenosoft.de>
2024-09-28 7:40 ` FSL P5040 board doesn't boot after DRM updates (drm-next-2024-09-19) Christian Zigotzky
2024-09-28 8:08 ` mad skateman
2024-09-28 8:42 ` Christophe Leroy
2024-09-28 11:46 ` Christian Zigotzky
2024-09-28 12:15 ` Christian Zigotzky
2024-09-29 14:37 ` Christian Zigotzky
2024-09-30 13:26 ` Alex Deucher [this message]
2024-10-01 4:26 ` Kernel " Christian Zigotzky
2024-10-01 12:09 ` Hoi Pok Wu
2024-10-01 12:23 ` Christophe Leroy
2024-10-01 14:41 ` Hoi Pok Wu
2024-10-02 13:43 ` Hoi Pok Wu
2024-10-03 4:57 ` Christian Zigotzky
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=CADnq5_PB8zUfCN-NcNpgHqzAv8A55o2hsYHAdnSBhEy525NLfA@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=christophe.leroy@csgroup.eu \
--cc=chzigotzky@xenosoft.de \
--cc=darren@stevens-zone.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=hypexed@yahoo.com.au \
--cc=info@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madskateman@gmail.com \
--cc=rtd2@xtra.co.nz \
--cc=wuhoipok@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;
as well as URLs for NNTP newsgroup(s).