public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@cygnus.co.uk>
To: "Ling Su" <lingsu@palmmicro.com>
Cc: "Jonathan Larmour" <jlarmour@redhat.com>,
	<ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] How to access PCI memory(HELP)....
Date: Tue, 12 Sep 2000 02:33:00 -0000	[thread overview]
Message-ID: <pou2bmneja.fsf@balti.cygnus.co.uk> (raw)
In-Reply-To: <001e01c01c20$a6e1c900$0201a8c0@raccoon>

"Ling Su" <lingsu@palmmicro.com> writes:

> Why need I set HAL_PCI_ALLOC_BASE_MEMORY to 0x90000000, originally it is
> 0x0, which means mapp the memory from the beginning, what is the rational to
> add a 0x9000_0000 offset?

Since the 4372 is already mapped at 0x80000000 in the PCI space, any
further allocations must be contiguous with that, since the aperture
onto the PCI address space starts there.

> Nick, I follow your suggestion, basically I changed three things,
> (1). HAL_PCI_PHYSICAL_MEMORY_BASE set to 0xD0000000
> (2). HAL_PCI_ALLOC_BASE_MEMORY set to 0x90000000
> (3). increase NUMB_PG to 16
> 


>  BAR[0]    0x09000000 / probed size 0xFFF00000 / CPU addr 0xD9000000

These look like the value of HAL_PCI_ALLOC_BASE_MEMORY is
0x09000000 rather than 0x90000000 - a missing zero most probably.
Also the value of CPU addr suggests that HAL_PCI_PHYSICAL_MEMORY_BASE
should be 0x40000000, since that is the offset between a PCI address
and its virtual address in the CPU.

So try these values:

HAL_PCI_PHYSICAL_MEMORY_BASE = 0x40000000
HAL_PCI_ALLOC_BASE_MEMORY = 0x90000000
NUMB_PG = 16


Let me know what happens.

-- 
Nick Garnett, eCos Kernel Architect
Red Hat, Cambridge, UK

  reply	other threads:[~2000-09-12  2:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-08 11:43 Ling Su
2000-09-10 19:44 ` Jonathan Larmour
2000-09-10 19:48   ` Jonathan Larmour
2000-09-10 20:39     ` Ling Su
2000-09-10 21:29       ` Jonathan Larmour
2000-09-11  3:59         ` Nick Garnett
2000-09-11 11:47           ` Ling Su
2000-09-12  2:33             ` Nick Garnett [this message]
2000-09-12 12:10             ` Ling Su
2000-09-12 16:56               ` Ling Su
2000-09-13  3:04                 ` Nick Garnett
2000-09-11 11:34         ` Ling Su
2000-09-11 11:38           ` Jonathan Larmour
2000-09-11 11:39         ` Ling Su
2000-09-11 21:05 [ECOS] Fw: " Ling Su
2000-09-12  2:56 ` [ECOS] " Nick Garnett
2000-09-12 11:07   ` Ling Su
2000-09-13  3:09     ` Nick Garnett
2002-06-13  4:59 namita  chawla
2002-06-13  9:20 ` David N. Welton
2002-06-13  9:28   ` Stephen Polkowski

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=pou2bmneja.fsf@balti.cygnus.co.uk \
    --to=nickg@cygnus.co.uk \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jlarmour@redhat.com \
    --cc=lingsu@palmmicro.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).