linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Korpilla <okorpil@fh-landshut.de>
To: "Heater, Daniel (GE Infrastructure)" <Daniel.Heater@gefanuc.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: VME - PowerPC: Resource sizes
Date: Thu, 10 Jun 2004 09:32:54 +0200	[thread overview]
Message-ID: <40C80EA6.1060005@fh-landshut.de> (raw)
In-Reply-To: <DB1DE297F535B340AEAE1E51B221C3D007E84017@FTWMLVEM02.e2k.ad.ge.com>


Heater, Daniel (GE Infrastructure) wrote:

>>I don't know about x86 bus organization, but maybe it limits
>>the address
>>range for available addresses too strongly (on a single bus,
>>where the
>>Universe is on). Comparing how much window space you can map with the
>>old version and the new one on x86 could prove useful.
>>
>>
>
>Your dead on right. I cannot allocate as much space. In fact,
>on a VMIVME-7750 I'm only able to allocate 768KB now vs. the
>~2MB I could access before.
>
>
Since we only request the current bus the Universe is on, there could be
a fix:
We could iterate the PCI bus tree to the top (there is some parent bus
field, IIRC), and then start complete iteration until a suitable
resource is found. This may produce larger resource regions with
reasonable effort.

Are you sure you mean 768 _KB_ and 2 _MB_, not 768 _MB_ and 2 _GB_? My
SLSI window is already 64 MB big, and with the PCI layout on my MVME2100
it is imaginable that I could map 84000000 - BEFFFFFF = 944MB (from end
of SLSI window to start of the Universe I/O memory)?

With kind regards,
Oliver Korpilla

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-06-10  7:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 20:01 VME driver patch for PowerPC Heater, Daniel (GE Infrastructure)
2004-06-10  7:32 ` Oliver Korpilla [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-10 13:03 VME - PowerPC: Resource sizes Heater, Daniel (GE Infrastructure)
2004-06-10 15:11 ` Oliver Korpilla

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=40C80EA6.1060005@fh-landshut.de \
    --to=okorpil@fh-landshut.de \
    --cc=Daniel.Heater@gefanuc.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 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).