From: Farhan Ali <alifm@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linux-fbdev@vger.kernel.org
Cc: schwidefsky@de.ibm.com, borntraeger@de.ibm.com,
stefan.kristiansson@saunalahti.fi, tomi.valkeinen@ti.com
Subject: [PATCH v1 0/2] Kconfig changes to enable Graphics Support for S390
Date: Thu, 25 Jan 2018 15:47:29 +0000 [thread overview]
Message-ID: <cover.1516892845.git.alifm@linux.vnet.ibm.com> (raw)
Hi,
This series of patches are in preparation for enabling an additional
tty and console for a S390 KVM guest using a virtio-gpu device[1].
One of the steps to do this would be to enable CONFIG_VT for S390,
and this would also require the dummy console (CONFIG_DUMMY_CONSOLE).
Patch 1 enables the "Graphics support" menu which is
needed to enable dummy console, since the VT layer needs it.
Patch 2 fixes a Kconfig dependency issue for opencores
framebuffer devices. This issue was exposed by the previous
patch.
Thanks
Farhan
[1] https://lists.nongnu.org/archive/html/qemu-devel/2017-09/msg04184.html
Farhan Ali (2):
Kconfig : Remove HAS_IOMEM dependency for Graphics support
fbdev: Kconfig: Add HAS_IOMEM dependency for FB_OPENCORES
drivers/video/Kconfig | 1 -
drivers/video/fbdev/Kconfig | 2 +-
2 files changed, 1 insertion(+), 2 deletions(-)
--
2.7.4
next reply other threads:[~2018-01-25 15:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 15:47 Farhan Ali [this message]
2018-01-25 15:47 ` [PATCH v1 1/2] Kconfig : Remove HAS_IOMEM dependency for Graphics support Farhan Ali
2018-01-26 12:31 ` Thomas Huth
2018-01-25 15:47 ` [PATCH v1 2/2] fbdev: Kconfig: Add HAS_IOMEM dependency for FB_OPENCORES Farhan Ali
2018-01-26 12:33 ` Thomas Huth
2018-01-26 12:38 ` Tomi Valkeinen
2018-01-26 14:32 ` Farhan Ali
2018-01-26 13:41 ` [PATCH v1 0/2] Kconfig changes to enable Graphics Support for S390 Geert Uytterhoeven
2018-01-26 14:35 ` Farhan Ali
2018-01-26 15:06 ` Geert Uytterhoeven
2018-01-26 16:26 ` Farhan Ali
2018-01-30 13:22 ` Christian Borntraeger
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=cover.1516892845.git.alifm@linux.vnet.ibm.com \
--to=alifm@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=stefan.kristiansson@saunalahti.fi \
--cc=tomi.valkeinen@ti.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).