From: Dag Nygren <dag@newtech•fi>
To: linuxppc-embedded@lists•linuxppc.org
Subject: PCI confusion
Date: Thu, 15 Feb 2001 19:54:33 +0200 [thread overview]
Message-ID: <20010215175433.8317.qmail@dag.newtech.fi> (raw)
Hi,
I just got a 2.2.17 port working OK and started
with the 2.4.1 (from www.kernel.org).
I used the same BAT mapping and replaced my
old PCI mapping code with the one in arch/ppc/kernel/pci.c.
Now I am confused.....
The BAT maps PCI MEM space from 0xc0000000 to 0xe0000000 in
mm/init.c.
The PCI devices can bee seen fine when printing ie. the first one
in pci.c, after the fixup of the addresses. (with address 0xexxxxxxx).
But later when the driver tries to access the PCI devices memory space
the kernel oops:es with a memory access error (11).
What could I have overlooked?
What changed from 2.2.17 to 2.4.1 on the PCI side ?
BRGDS
--
Dag Nygren email: dag@newtech•fi
Oy NewTech Ab phone: +358 9 8024910
Trasktorpet 3 fax: +358 9 8024916
02360 ESBO GSM: 0400-426312
FINLAND
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-02-15 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 17:54 Dag Nygren [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-08 15:54 PCI confusion Dag Nygren
2001-03-08 13:01 ` Matt Porter
2001-03-08 14:54 ` Matt Porter
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=20010215175433.8317.qmail@dag.newtech.fi \
--to=dag@newtech$(echo .)fi \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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