public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ruiyu Ni <ruiyu.ni@intel.com>
To: edk2-devel@lists.01.org
Cc: Star Zeng <star.zeng@intel.com>
Subject: [PATCH 0/2] MdeModulePkg/PciBus: Restrict one VGA per HostBridge not Segment
Date: Thu, 23 Aug 2018 10:53:51 +0800	[thread overview]
Message-ID: <20180823025353.137924-1-ruiyu.ni@intel.com> (raw)

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1109

Today's restriction of VGA device is to have only one VGA device
enabled per PCI segment. It's not correct because several segments
may share one IO / MMIO address space.
We should restrict to have one VGA per Host Bridge because each
Host Bridge has its only IO / MMIO address space.

Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
Cc: Star Zeng <star.zeng@intel.com>

Ruiyu Ni (2):
  MdeModulePkg/PciBus: Refine ActiveVGADeviceOnTheRootBridge
  MdeModulePkg/PciBus: Restrict one VGA per HostBridge not Segment

 MdeModulePkg/Bus/Pci/PciBusDxe/PciDeviceSupport.c | 55 +++++++++++------------
 MdeModulePkg/Bus/Pci/PciBusDxe/PciDeviceSupport.h | 20 ++++-----
 MdeModulePkg/Bus/Pci/PciBusDxe/PciIo.c            |  4 +-
 3 files changed, 38 insertions(+), 41 deletions(-)

-- 
2.16.1.windows.1



             reply	other threads:[~2018-08-23  2:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-23  2:53 Ruiyu Ni [this message]
2018-08-23  2:53 ` [PATCH 1/2] MdeModulePkg/PciBus: Refine ActiveVGADeviceOnTheRootBridge Ruiyu Ni
2018-08-24  8:13   ` Zeng, Star
2018-08-23  2:53 ` [PATCH 2/2] MdeModulePkg/PciBus: Restrict one VGA per HostBridge not Segment Ruiyu Ni
2018-08-24  8:16   ` Zeng, Star

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-list 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=20180823025353.137924-1-ruiyu.ni@intel.com \
    --to=devel@edk2.groups.io \
    /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