From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please pull u-boot-video
Date: Mon, 10 Jun 2019 12:06:29 +0200 [thread overview]
Message-ID: <20190610120629.16110abd@crub> (raw)
Hi Tom,
please pull video fixes and mxsfb DM_VIDEO conversion for v2019.07.
Travis CI: https://travis-ci.org/vdsao/u-boot-video/builds/541462360
Thanks,
Anatolij
The following changes since commit 38c2a8a00132b4dcc6a0bb5baf5146b9eb9eb2d2:
Merge tag 'efi-2019-07-rc4' of git://git.denx.de/u-boot-efi (2019-06-02 18:19:45 -0400)
are available in the Git repository at:
git://git.denx.de/u-boot-video.git tags/video-updates-for-2019.07-rc3
for you to fetch changes up to f944b15966d410fd81f6051a836f86d5263f617e:
video: meson: hdmi-supply regulator should be optional (2019-06-05 10:51:46 +0200)
----------------------------------------------------------------
- mxsfb DM_VIDEO conversion
- splash fix for DM_VIDEO configurations
- meson HDMI fix for boards without hdmi-supply regulator
----------------------------------------------------------------
Igor Opaniuk (8):
splash: display splash in DM_VIDEO configurations
colibri imx6/t20: enable CONFIG_SYS_WHITE_ON_BLACK
video: mxsfb: change mxs_lcd_init signature
video: mxsfb: reorder includes
video: mxsfb: refactor video_hw_init()
video: mxsfb: add DM_VIDEO support
ARM: dts: colibri_imx7: Add lcdif node
colibri_imx7_emmc: enable DM_VIDEO
Maxime Jourdan (1):
video: meson: hdmi-supply regulator should be optional
arch/arm/dts/imx7-colibri-emmc.dts | 2 +
arch/arm/dts/imx7-colibri.dtsi | 28 +++++
arch/arm/mach-imx/cpu.c | 2 +-
arch/arm/mach-imx/mx7/soc.c | 2 +-
common/lcd.c | 13 +--
common/splash.c | 16 ++-
common/stdio.c | 4 +
configs/colibri_imx6_defconfig | 1 +
configs/colibri_imx7_emmc_defconfig | 2 +-
configs/colibri_t20_defconfig | 1 +
drivers/video/meson/meson_dw_hdmi.c | 14 ++-
drivers/video/mxsfb.c | 219 +++++++++++++++++++++++++++++-------
include/configs/colibri_imx7.h | 2 +-
include/splash.h | 6 +-
14 files changed, 250 insertions(+), 62 deletions(-)
next reply other threads:[~2019-06-10 10:06 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 10:06 Anatolij Gustschin [this message]
2019-06-11 1:31 ` [U-Boot] Please pull u-boot-video Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2019-11-24 21:07 Anatolij Gustschin
2019-11-25 22:22 ` Tom Rini
2019-11-18 10:39 Anatolij Gustschin
2019-11-18 20:27 ` Tom Rini
2019-10-31 13:35 Anatolij Gustschin
2019-11-01 21:48 ` Tom Rini
2019-11-01 23:05 ` Anatolij Gustschin
2019-10-14 9:40 Anatolij Gustschin
2019-10-14 17:00 ` Tom Rini
2019-09-22 19:50 Anatolij Gustschin
2019-09-23 0:39 ` Tom Rini
2019-07-30 18:07 Anatolij Gustschin
2019-07-31 12:34 ` Tom Rini
2019-07-29 9:09 Anatolij Gustschin
2019-07-30 1:21 ` Tom Rini
2019-07-07 13:58 Anatolij Gustschin
2019-07-08 1:15 ` Tom Rini
2019-05-20 14:39 Anatolij Gustschin
2019-05-21 15:44 ` Tom Rini
2019-04-14 18:10 Anatolij Gustschin
2019-04-17 13:14 ` Tom Rini
2019-03-29 21:37 Anatolij Gustschin
2019-04-01 13:13 ` Tom Rini
2019-02-16 22:57 Anatolij Gustschin
2019-02-18 14:29 ` Tom Rini
2019-01-31 12:36 Anatolij Gustschin
2019-01-31 12:40 ` Anatolij Gustschin
2019-02-01 13:26 ` Tom Rini
2019-01-03 18:48 Anatolij Gustschin
2019-01-04 13:11 ` Tom Rini
2018-12-05 0:53 Anatolij Gustschin
2018-12-06 1:31 ` Tom Rini
2010-04-27 21:31 Anatolij Gustschin
2010-04-27 22:10 ` Wolfgang Denk
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=20190610120629.16110abd@crub \
--to=agust@denx.de \
--cc=u-boot@lists.denx.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