From: Paul Mackerras <paulus@cs.anu.edu.au>
To: hozer@drgw.net
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: ioremap (still?) broken
Date: Wed, 8 Sep 1999 11:03:29 +1000 [thread overview]
Message-ID: <199909080103.LAA02277@tango.anu.edu.au> (raw)
In-Reply-To: <Pine.LNX.4.04.9909070126490.14821-100000@narn.drgw.net> (message from Troy Benjegerdes on Tue, 7 Sep 1999 01:44:38 -0500 (CDT))
Troy Benjegerdes <hozer@drgw.net> wrote:
> The alteon driver does an 'ioremap' on the address provided by the kernel
> PCI services, and then expects to be able to access the PCI card's memory
> via accessing the memory returned using 'readl,writel'.
That should work.
> The first thing the driver does is check the card version by reading a
> particular register. By using appropriate printf's, I have found that the
> value returned is '0xffffffff'. (defininitely NOT the register it's
> looking for)
Possibly you may need to enable PCI memory or I/O space responses in
the PCI command register in the card's configuration space.
> Before I go on a wild chase again, could someone let me know whether the
> 2.2.12 kernel might have a better chance with this, or will I need to go
I just checked in a fix to ioremap in the vger 2.2 branch which fixes
the case where the mapping added by ioremap is the first in a 4MB
region. You would be getting kernel DSI exceptions (page faults) if
you had hit that bug, though.
Paul.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-09-08 1:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-07 6:44 ioremap (still?) broken Troy Benjegerdes
1999-09-07 6:55 ` Geert Uytterhoeven
1999-09-08 1:03 ` Paul Mackerras [this message]
1999-09-09 6:29 ` Michel Lanners
1999-09-10 3:07 ` Troy Benjegerdes
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=199909080103.LAA02277@tango.anu.edu.au \
--to=paulus@cs.anu.edu.au \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=hozer@drgw.net \
--cc=linuxppc-dev@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).