mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Linn <John.Linn@xilinx.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux@arm.linux.org.uk>,
	<catalin.marinas@arm.com>, <glikely@secretlab.ca>,
	<jamie@jamieiles.com>
Subject: RE: [PATCH V5 3/4] ARM: Xilinx: base header files and assembly macros
Date: Wed, 30 Mar 2011 07:37:10 -0600	[thread overview]
Message-ID: <807f31a6-c9ff-4f35-bece-e0222a8e1fda@VA3EHSMHS006.ehs.local> (raw)
In-Reply-To: <201103301529.03648.arnd@arndb.de>

> -----Original Message-----
> From: Arnd Bergmann [mailto:arnd@arndb.de]
> Sent: Wednesday, March 30, 2011 7:29 AM
> To: John Linn
> Cc: linux-arm-kernel@lists.infradead.org;
linux-kernel@vger.kernel.org;
> linux@arm.linux.org.uk; catalin.marinas@arm.com; glikely@secretlab.ca;
> jamie@jamieiles.com
> Subject: Re: [PATCH V5 3/4] ARM: Xilinx: base header files and
assembly
> macros
> 
> On Wednesday 30 March 2011, John Linn wrote:
> > Yes that makes sense.  We don't have immediate plans for PCI and
> > I was assuming when we add PCI we would need to change that.
> >
> > If you think I shouldn't put it off then I'll fix it now.  My
> > preference was to get the platform supported, then add more
features.
> 
> Getting it fixed properly depends a bit on the PCI implementation.
> I've been planning to clean up this part of the ARM architecture
> for some time and I can probably do it for one more platform when
> I get to it.

Sounds like it's fine to postpone it til we do PCI as I don't know all
the
details of the system yet. Soft logic in FPGAs is great :)

> 
> My idea for the multiplatform kernel is to have a global I/O space
> window (maybe 1 MB) that is in the same location in the virtual
> address space all the time, so any platform that wants to support
> PCI with direct-mapped I/O space can simply map it in there
> at boot time.
> 

Sounds like that will make it easier for everyone and more consistent.

Thanks,
John

> 	Arnd


This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.



  reply	other threads:[~2011-03-30 13:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1301444651-18008-1-git-send-email-john.linn@xilinx.com>
2011-03-30  0:24 ` [PATCH V5 1/4] ARM: Xilinx: Adding Xilinx board support John Linn
     [not found] ` <1301444651-18008-2-git-send-email-john.linn@xilinx.com>
2011-03-30  0:24   ` [PATCH V5 2/4] ARM: Xilinx: Adding timer support to the platform John Linn
     [not found]   ` <1301444651-18008-3-git-send-email-john.linn@xilinx.com>
2011-03-30  0:24     ` [PATCH V5 3/4] ARM: Xilinx: base header files and assembly macros John Linn
2011-03-30 11:44       ` Arnd Bergmann
2011-03-30 13:17         ` John Linn
2011-03-30 13:29           ` Arnd Bergmann
2011-03-30 13:37             ` John Linn [this message]
2011-03-30 19:15             ` Russell King - ARM Linux
2011-03-30 19:43               ` Arnd Bergmann
     [not found]     ` <1301444651-18008-4-git-send-email-john.linn@xilinx.com>
2011-03-30  0:24       ` [PATCH V5 4/4] ARM: Xilinx: Adding Xilinx platform infrastructure support John Linn
     [not found] <1298929919-510-1-git-send-email-john.linn@xilinx.com>
     [not found] ` <1298929919-510-2-git-send-email-john.linn@xilinx.com>
     [not found]   ` <1298929919-510-3-git-send-email-john.linn@xilinx.com>
2011-02-28 21:51     ` [PATCH V5 3/4] ARM: Xilinx: base header files and assembly macros John Linn

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=807f31a6-c9ff-4f35-bece-e0222a8e1fda@VA3EHSMHS006.ehs.local \
    --to=john.linn@xilinx.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=glikely@secretlab.ca \
    --cc=jamie@jamieiles.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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

all inboxes | Powered by JetHome®