From: "Bradley D. LaRonde" <brad@ltc.com>
To: "atul srivastava" <atulsrivastava9@rediffmail.com>,
<linux-mips@linux-mips.org>
Subject: Re: mips kseg1 mapping..
Date: Fri, 27 Sep 2002 11:15:36 -0400 [thread overview]
Message-ID: <048701c26638$bb357640$bc00a8c0@prefect> (raw)
In-Reply-To: 20020927144641.23180.qmail@mailweb33.rediffmail.com
----- Original Message -----
From: "atul srivastava" <atulsrivastava9@rediffmail.com>
To: <linux-mips@linux-mips.org>
Sent: Friday, September 27, 2002 10:46 AM
Subject: mips kseg1 mapping..
> 1.PCI BAR 1 of my eepro100 card has been initialised with
> address 0x18800100 for 64 bytes.
> this is a valid PCI IO address as per manual.
>
> 2.what i understand is that lower 0 - 512 MB physical is mapped to
> 0xa000-0000 to 0xb7ff-ffff virtual and also access to this range
> in uncached.
>
> 3.when i am loading my eepro100 driver , in do_eeprom_cmd() when
> it refers the address( ioaddr + SCBeeprom) my kernel panicks with
> message "unable to handle kernel paging request at 0xd100010e.
>
> this virtual address is in range 0xa000-0000 to 0xb7ff-ffff.
KSEG1 is always mapped (you can think of it as wired).
PCI bus addresses should be remapped through ioremap. Is ioremap returning
the address you expect?
Regards,
Brad
WARNING: multiple messages have this Message-ID (diff)
From: "Bradley D. LaRonde" <brad@ltc.com>
To: atul srivastava <atulsrivastava9@rediffmail.com>,
linux-mips@linux-mips.org
Subject: Re: mips kseg1 mapping..
Date: Fri, 27 Sep 2002 11:15:36 -0400 [thread overview]
Message-ID: <048701c26638$bb357640$bc00a8c0@prefect> (raw)
Message-ID: <20020927151536.C1drUHFacd0sF0JN_op7Z4rWW8mbbXgAeonNdksN_os@z> (raw)
In-Reply-To: 20020927144641.23180.qmail@mailweb33.rediffmail.com
----- Original Message -----
From: "atul srivastava" <atulsrivastava9@rediffmail.com>
To: <linux-mips@linux-mips.org>
Sent: Friday, September 27, 2002 10:46 AM
Subject: mips kseg1 mapping..
> 1.PCI BAR 1 of my eepro100 card has been initialised with
> address 0x18800100 for 64 bytes.
> this is a valid PCI IO address as per manual.
>
> 2.what i understand is that lower 0 - 512 MB physical is mapped to
> 0xa000-0000 to 0xb7ff-ffff virtual and also access to this range
> in uncached.
>
> 3.when i am loading my eepro100 driver , in do_eeprom_cmd() when
> it refers the address( ioaddr + SCBeeprom) my kernel panicks with
> message "unable to handle kernel paging request at 0xd100010e.
>
> this virtual address is in range 0xa000-0000 to 0xb7ff-ffff.
KSEG1 is always mapped (you can think of it as wired).
PCI bus addresses should be remapped through ioremap. Is ioremap returning
the address you expect?
Regards,
Brad
next prev parent reply other threads:[~2002-09-27 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-27 14:46 mips kseg1 mapping atul srivastava
2002-09-27 15:15 ` Bradley D. LaRonde [this message]
2002-09-27 15:15 ` Bradley D. LaRonde
2002-09-27 15:22 ` Ralf Baechle
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='048701c26638$bb357640$bc00a8c0@prefect' \
--to=brad@ltc.com \
--cc=atulsrivastava9@rediffmail.com \
--cc=linux-mips@linux-mips.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