From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Vitaly Bordug <vitb@kernel.crashing.org>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] [RFC][POWERPC] Merge 32 and 64 bit pci_process_bridge_OF_ranges() instances
Date: Wed, 19 Sep 2007 07:41:38 +1000 [thread overview]
Message-ID: <1190151698.6403.114.camel@localhost.localdomain> (raw)
In-Reply-To: <20070911224952.9838.46644.stgit@localhost.localdomain>
On Wed, 2007-09-12 at 02:49 +0400, Vitaly Bordug wrote:
> We are having 2 different instances of pci_process_bridge_OF_ranges(),
> which makes describing 64-bit physical addresses in non PPC64 case
> impossible.
>
> This approach inherits pci space parsing, but has a new way to behave
> equally good in both 32bit and 64bit environments. This approach uses
> of_translate_address(), so implies proper ranges <> definition in
> devicetree, where PCI node has its reg on soc bus, and its ranges
> effectively belong to LAW addresses.
Sorry for the delay, I was travelling.
NAK the bits with struct ranges_pci. Don't map structures to those DT
entries. Use a "cursor" pointer and some getter function, like
prom_parse does (maybe export the ones in prom_parse).
Ben.
next prev parent reply other threads:[~2007-09-18 21:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 22:49 [PATCH] [RFC][POWERPC] Merge 32 and 64 bit pci_process_bridge_OF_ranges() instances Vitaly Bordug
2007-09-11 22:57 ` Arnd Bergmann
2007-09-11 23:56 ` Vitaly Bordug
2007-09-12 8:13 ` Arnd Bergmann
2007-09-12 14:51 ` Segher Boessenkool
2007-09-12 16:07 ` Vitaly Bordug
2007-09-13 5:11 ` David Gibson
2007-09-18 12:03 ` Valentine Barshak
2007-09-18 14:27 ` Vitaly Bordug
2007-09-18 14:38 ` Valentine Barshak
2007-09-19 0:09 ` Vitaly Bordug
2007-09-18 21:44 ` Benjamin Herrenschmidt
2007-09-18 21:41 ` Benjamin Herrenschmidt [this message]
2007-09-18 21:42 ` Benjamin Herrenschmidt
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=1190151698.6403.114.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=vitb@kernel.crashing.org \
/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.