LKML Archive on
help / color / mirror / Atom feed
From: David Miller <>
Subject: Re: [PATCH v1 0/2] PCI: Sparc 64-bit resource fixups
Date: Sun, 18 Mar 2018 12:07:34 -0400 (EDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

From: Bjorn Helgaas <>
Date: Tue, 20 Feb 2018 17:39:35 -0600

> Both these patches are on my pci/sparc branch and appeared in the
> Feb 19 linux-next tree.
> Any testing and feedback (especially on the second patch, which should
> change /proc/iomem) would be great.
> They're headed for v4.17 unless I hear about issues.
> It would be useful to hear about what's still broken so I can try to
> pull in the other patches.

I don't understand why you put the SYSTEM and Video ROM at addresses
relative to absolute zero.  The result of this is that it might
overlap real physical memory.

If a VGA card is present, it's ROM will respond to those addresses
relative to the PCI controller's MEM space area.

Their legacy resources are "hardwired", but those hardwired addresses
need to be relative to the PCI host controller's MEM areas in order
for them to be accessible.

I could understand removing the System ROM resource altogether, that
makes a lot of sense to me.


  parent reply	other threads:[~2018-03-18 16:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-15 15:17 Bjorn Helgaas
2018-02-15 15:18 ` [PATCH v1 1/2] sparc/PCI: Support arbitrary host bridge address offset Bjorn Helgaas
2018-02-15 15:18 ` [PATCH v1 2/2] sparc/PCI: Reserve System ROM and Video ROM outside of PCI space Bjorn Helgaas
2018-02-20 23:39 ` [PATCH v1 0/2] PCI: Sparc 64-bit resource fixups Bjorn Helgaas
2018-02-21 20:37   ` Khalid Aziz
2018-03-18 16:07   ` David Miller [this message]
2018-03-19 17:11     ` Bjorn Helgaas
2018-03-19 18:28       ` David Miller
2018-03-19 19:38         ` Bjorn Helgaas
2018-03-19 23:33           ` David Miller
2018-03-20 20:14             ` Bjorn Helgaas

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH v1 0/2] PCI: Sparc 64-bit resource fixups' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).