All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	linux-pci@vger.kernel.org,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation
Date: Sat, 30 Apr 2016 00:03:55 +0200	[thread overview]
Message-ID: <5723DA4B.5010501@suse.de> (raw)
In-Reply-To: <5723D7AF.3080108@suse.de>



On 29.04.16 23:52, Alexander Graf wrote:
> 
> 
> On 29.04.16 23:37, Bjorn Helgaas wrote:
>
> Can you point me to the code that does "read[ing] the BARs"? So far my
> impression was that we don't even try to read out the current BAR values
> from pci config space, but I can't claim I fully grasp the Linux pci
> code quite yet.

I should've probably read Lorenzos email more closely before - it
contains the pointer.


Alex

WARNING: multiple messages have this Message-ID (diff)
From: agraf@suse.de (Alexander Graf)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation
Date: Sat, 30 Apr 2016 00:03:55 +0200	[thread overview]
Message-ID: <5723DA4B.5010501@suse.de> (raw)
In-Reply-To: <5723D7AF.3080108@suse.de>



On 29.04.16 23:52, Alexander Graf wrote:
> 
> 
> On 29.04.16 23:37, Bjorn Helgaas wrote:
>
> Can you point me to the code that does "read[ing] the BARs"? So far my
> impression was that we don't even try to read out the current BAR values
> from pci config space, but I can't claim I fully grasp the Linux pci
> code quite yet.

I should've probably read Lorenzos email more closely before - it
contains the pointer.


Alex

  reply	other threads:[~2016-04-29 22:03 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27 22:22 [PATCH] arm64: Relocate screen_info.lfb_base on PCI BAR allocation Alexander Graf
2016-04-27 22:22 ` Alexander Graf
2016-04-28 16:20 ` Bjorn Helgaas
2016-04-28 16:20   ` Bjorn Helgaas
2016-04-28 16:41   ` Alexander Graf
2016-04-28 16:41     ` Alexander Graf
2016-04-28 18:06     ` Bjorn Helgaas
2016-04-28 18:06       ` Bjorn Helgaas
2016-04-28 21:39       ` Alexander Graf
2016-04-28 21:39         ` Alexander Graf
2016-04-29 10:03         ` Lorenzo Pieralisi
2016-04-29 10:03           ` Lorenzo Pieralisi
2016-04-29 13:41         ` Bjorn Helgaas
2016-04-29 13:41           ` Bjorn Helgaas
2016-04-29 13:51           ` Ard Biesheuvel
2016-04-29 13:51             ` Ard Biesheuvel
2016-04-29 13:51             ` Ard Biesheuvel
2016-04-29 20:06             ` Bjorn Helgaas
2016-04-29 20:06               ` Bjorn Helgaas
2016-04-29 20:06               ` Bjorn Helgaas
2016-04-29 20:25               ` Ard Biesheuvel
2016-04-29 20:25                 ` Ard Biesheuvel
2016-04-29 20:25                 ` Ard Biesheuvel
2016-04-29 20:51                 ` Alexander Graf
2016-04-29 20:51                   ` Alexander Graf
2016-04-29 20:51                   ` Alexander Graf
2016-04-29 21:37                   ` Bjorn Helgaas
2016-04-29 21:37                     ` Bjorn Helgaas
2016-04-29 21:37                     ` Bjorn Helgaas
2016-04-29 21:52                     ` Alexander Graf
2016-04-29 21:52                       ` Alexander Graf
2016-04-29 21:52                       ` Alexander Graf
2016-04-29 22:03                       ` Alexander Graf [this message]
2016-04-29 22:03                         ` Alexander Graf
2016-04-29 22:03                         ` Alexander Graf
2016-04-29 23:31                       ` Bjorn Helgaas
2016-04-29 23:31                         ` Bjorn Helgaas
2016-04-29 23:31                         ` Bjorn Helgaas
2016-04-30 21:17                         ` Matt Fleming
2016-04-30 21:17                           ` Matt Fleming
2016-04-30 21:17                           ` Matt Fleming
2016-04-29 21:20                 ` Bjorn Helgaas
2016-04-29 21:20                   ` Bjorn Helgaas
2016-04-29 21:20                   ` 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:
  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=5723DA4B.5010501@suse.de \
    --to=agraf@suse.de \
    --cc=ard.biesheuvel@linaro.org \
    --cc=helgaas@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.