From: Lucas Stach <l.stach@pengutronix.de>
To: "Yazdani, Reyhaneh" <RYazdani@data-modul.com>,
"barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: signed HDMI firmware in imx8mq image
Date: Wed, 16 Jan 2019 10:34:50 +0100 [thread overview]
Message-ID: <1547631290.4339.26.camel@pengutronix.de> (raw)
In-Reply-To: <a47578bb-9855-9645-e48b-fc9d3478a173@data-modul.com>
Hi Reyhaneh,
Am Mittwoch, den 16.01.2019, 08:48 +0000 schrieb Yazdani, Reyhaneh:
> Every one,
>
> In order to build a Barebox image to boot imx8mq-evk with HDMI, I have tried to
> tell Barebox about the embedded signed HDMI firmware, which is necessary for
> provided kernel image by NXP.
>
> for this matter, I added the below line into the
> arch/arm/boards/nxp-imx8mq-evk/flash-header-imx8mq-evk.imxcfg
>
> soc imx8mq
> loadaddr 0x007E1000
> dcdofs 0x400
> + signed_hdmi_firmware firmware/imx/signed_hdmi_imx8m.bin
>
> And placed the firmware into the build-directory/firmware/imx
>
>
> By checking kernel boot message, it seems the HDMI FW is running, but no access
> to the HDMI:
> [drm:hdmi_phy_init_t28hpc] *ERROR* HDMI mailbox access failed
>
> What should I do more in Barebox to make HDMI accessible by kernel?
I don't think there is anything more needed from the Barebox side. At
least the same change works for me and gets me a working HDMI display
on the EVK board.
I don't use the NXP kernel through, but running a 4.20 based kernel
with lot of downstream bits ported. This might be a incompatibility of
your kernel with the imx8 ATF version shipped with Barebox.
Regards,
Lucas
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-01-16 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 8:48 Yazdani, Reyhaneh
2019-01-16 9:34 ` Lucas Stach [this message]
2019-01-16 20:30 ` Andrey Smirnov
2019-01-17 10:04 ` Yazdani, Reyhaneh
2019-01-23 10:43 ` Yazdani, Reyhaneh
2019-01-17 8:19 ` Yazdani, Reyhaneh
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=1547631290.4339.26.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=RYazdani@data-modul.com \
--cc=barebox@lists.infradead.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