From: "Ling Su" <lingsu@palmmicro.com>
To: "Jonathan Larmour" <jlarmour@redhat.com>
Cc: <ecos-discuss@sources.redhat.com>, "Nick Garnett" <nickg@redhat.com>
Subject: Re: [ECOS] How to access PCI memory(HELP)....
Date: Mon, 11 Sep 2000 11:34:00 -0000 [thread overview]
Message-ID: <000d01c01c1e$d9162e40$0201a8c0@raccoon> (raw)
In-Reply-To: <39BC5F8F.695822B4@redhat.com>
Jifl said,
>
> After another look I now see what's going on. Yes, there is a problem here
> I believe and some of my understanding before was wrong(!) The relevant
> stuff is in hal_memc_setup_table (a table-driven initialization thing
> driven by hal_memc_setup) in platform.S.
>
> In there, PCI_IOSPACE_BASE is set to 0x0c. This is used at the entry:
>
> # Map PCI IO space Phys == Local
> .long PCIMSTRIO, (0x000fd000 | ( PCI_IOSPACE_BASE << 24) |
> PCI_IOSPACE_BASE)
>
> So while the space is being mapped 1:1, it is indeed set up for 0x0C000000
> and not 0xC0000000, as you suggested.
>
> The fix may be just changing the definition of
> HAL_PCI_PHYSICAL_MEMORY_BASE in plf_io.h to 0x0C000000
>
> Give that a go and let us know if it worked.
>
Thanks, Jifl,
I think Nick said is correct, "PCI_IOSPACE_BASE only maps PCI device IO
registers, not memory
mappings ". I still try what you suggested, change the
HAL_PCI_PHYSICAL_MEMORY_BASE to 0x0C00_0000, unfortunately the is a SIGSEGV
signal, and a segment fault. I didn't dig the codes on the MMU part, and
don't know if the eCos actived TLB in VR4300, I have grabbed a copy of
vr4300 manual, hopefully I can find anything helpful.... but I don't know if
I could still catch up my project scedule...:) if you have any thing new to
update, kindly let me know, thanks a lot!
Best Regards,
-Ling
next prev parent reply other threads:[~2000-09-11 11:34 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
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 [this message]
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='000d01c01c1e$d9162e40$0201a8c0@raccoon' \
--to=lingsu@palmmicro.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@redhat.com \
--cc=nickg@redhat.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).