* RE: 440GX: mapping PCI address
@ 2004-07-27 18:20 Barbier, Renaud (GE Infrastructure)
2004-07-27 20:29 ` Matt Porter
0 siblings, 1 reply; 6+ messages in thread
From: Barbier, Renaud (GE Infrastructure) @ 2004-07-27 18:20 UTC (permalink / raw)
To: linuxppc-embedded
ok. I am lost here.
I have checked the linux source code and can see
comments regarding fix for the 36-bit address.
So I would think the current BSP I have can support what I need.
Still even though I am getting an address from mmap access, to the location freezes my machine.
Here is the code.
fd=open("/dev/mem", O_RDWR);
/* test fd for error */
ptr=(unsigned int *)mmap(0, 4096, PROT_READ | PROT_WRITE,
MAP_SHARED, fd, 0xec00000); or /* 0x80002000 */
printf("ptr = 0x%x\n", (unsigned int)ptr);
the returned address is 0x30019000.
If I understand correctly 0x0ec00000 should be translated by the kernel
to 0x20ec00000 to map the PCI configuration register.
I can see the remapping being done when using ioremap in the drivers but not
when doing mmap at user level. So could be wrong in my system?
Actually, what do you do if you have 512MB of memory? I guess change the "trap" area.
-----Original Message-----
From: owner-linuxppc-embedded@lists.linuxppc.org
[mailto:owner-linuxppc-embedded@lists.linuxppc.org]On Behalf Of Gerhard
Jaeger
Sent: Thursday, July 22, 2004 12:48 PM
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 440GX: mapping PCI address
Hi,
checkout
arch/ppc/mm/pgtable.c
there you'll find the ioremap function which is used to remap physical
addresses. This function calls internaly fixup_big_physaddr(), defined in
arch/ppc/kernel/ibm44x_common.c
This fixup_big_physaddr() adjusts some 32bit addresses to some corresponding
36bit addresses, which can be mapped by the kernel by calling ioremap64.
Your example:
Calling mmap with the address 0x80002000 (see also include/asm-ppc/ibm44x.h)
will map the PCI area, by trapping this 0x80002000 and making a 36bit address
out of it. There a 3 "trap" areas defined:
/*
* 36-bit trap ranges
*/
#define PPC44x_IO_LO 0x40000000
#define PPC44x_IO_HI 0x40001000
#define PPC44x_PCICFG_LO 0x0ec00000
#define PPC44x_PCICFG_HI 0x0ec7ffff
#define PPC44x_PCIMEM_LO 0x80002000
#define PPC44x_PCIMEM_HI 0xffffffff
Hope this helps,
Gerhard
On Thursday 22 July 2004 11:58, Barbier, Renaud (GE Infrastructure) wrote:
> As you know the PCI address(and other embedded device) are seen through a
> 36-bit address space.
>
> How do you map this address from user space?
>
> I have seen a message from 2002 saying it is not supported. Anything new
> since then?
>
> thanks.
--
Gerhard Jaeger g.jaeger@sysgo.com
SYSGO AG Embedded and Real-Time Software
Voice: + 49 731 94683-0 Fax: + 49 731 94683-10
www.sysgo.com | www.elinos.com | www.osek.de | www.imerva.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: 440GX: mapping PCI address
2004-07-27 18:20 440GX: mapping PCI address Barbier, Renaud (GE Infrastructure)
@ 2004-07-27 20:29 ` Matt Porter
0 siblings, 0 replies; 6+ messages in thread
From: Matt Porter @ 2004-07-27 20:29 UTC (permalink / raw)
To: Barbier, Renaud (GE Infrastructure); +Cc: linuxppc-embedded
On Tue, Jul 27, 2004 at 01:20:27PM -0500, Barbier, Renaud (GE Infrastructure) wrote:
>
> ok. I am lost here.
> I have checked the linux source code and can see
> comments regarding fix for the 36-bit address.
> So I would think the current BSP I have can support what I need.
Did you get the patch I mentioned? It hacks remap_page_range() to
call the 36-bit fixups and handle a u64 phys addr. What "BSP"
are you talking about? Are you running a stock kernel tree?
> Still even though I am getting an address from mmap access, to the location freezes my machine.
> Here is the code.
> fd=open("/dev/mem", O_RDWR);
>
> /* test fd for error */
> ptr=(unsigned int *)mmap(0, 4096, PROT_READ | PROT_WRITE,
> MAP_SHARED, fd, 0xec00000); or /* 0x80002000 */
> printf("ptr = 0x%x\n", (unsigned int)ptr);
>
> the returned address is 0x30019000.
>
> If I understand correctly 0x0ec00000 should be translated by the kernel
> to 0x20ec00000 to map the PCI configuration register.
Only if the patch is applied.
> I can see the remapping being done when using ioremap in the drivers but not
> when doing mmap at user level. So could be wrong in my system?
>
>
> Actually, what do you do if you have 512MB of memory? I guess change the "trap" area.
I don't follow, how does 512MB of memory change things in your
case? The hack does make some assumptions but it works for most
peoples needs.
-Matt
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: 440GX: mapping PCI address
@ 2004-07-22 14:43 Barbier, Renaud (GE Infrastructure)
2004-07-22 16:20 ` Matt Porter
0 siblings, 1 reply; 6+ messages in thread
From: Barbier, Renaud (GE Infrastructure) @ 2004-07-22 14:43 UTC (permalink / raw)
To: linuxppc-embedded
> /*
> * 36-bit trap ranges
> */
> #define PPC44x_IO_LO 0x40000000
> #define PPC44x_IO_HI 0x40001000
> #define PPC44x_PCICFG_LO 0x0ec00000
> #define PPC44x_PCICFG_HI 0x0ec7ffff
> #define PPC44x_PCIMEM_LO 0x80002000
> #define PPC44x_PCIMEM_HI 0xffffffff
> Hope this helps,
> Gerhard
Indeed, I get a virtual address out of mmap
but my system freezes when I access it.
I try to access the PCI external configuration registers:
ptr=(unsigned int *)mmap(0, getpagesize(), PROT_READ | PROT_WRITE,
MAP_SHARED, fd, 0x0ec00000);
My kernel is 2.4.21 I would guess it should work from what I have seen regarding
messages about 36-bit address on 440GX.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: 440GX: mapping PCI address
2004-07-22 14:43 Barbier, Renaud (GE Infrastructure)
@ 2004-07-22 16:20 ` Matt Porter
0 siblings, 0 replies; 6+ messages in thread
From: Matt Porter @ 2004-07-22 16:20 UTC (permalink / raw)
To: Barbier, Renaud (GE Infrastructure); +Cc: linuxppc-embedded
On Thu, Jul 22, 2004 at 09:43:26AM -0500, Barbier, Renaud (GE Infrastructure) wrote:
> Indeed, I get a virtual address out of mmap
> but my system freezes when I access it.
> I try to access the PCI external configuration registers:
>
> ptr=(unsigned int *)mmap(0, getpagesize(), PROT_READ | PROT_WRITE,
> MAP_SHARED, fd, 0x0ec00000);
>
>
> My kernel is 2.4.21 I would guess it should work from what I have seen regarding
> messages about 36-bit address on 440GX.
Check the archives, I've posted a URL for the 36-bit mmap patch
several times.
-Matt (one who reads archives and googles to get FAQs answered :P)
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* 440GX: mapping PCI address
@ 2004-07-22 9:58 Barbier, Renaud (GE Infrastructure)
2004-07-22 11:47 ` Gerhard Jaeger
0 siblings, 1 reply; 6+ messages in thread
From: Barbier, Renaud (GE Infrastructure) @ 2004-07-22 9:58 UTC (permalink / raw)
To: linuxppc-embedded
As you know the PCI address(and other embedded device) are seen through a 36-bit address space.
How do you map this address from user space?
I have seen a message from 2002 saying it is not supported. Anything new since then?
thanks.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 440GX: mapping PCI address
2004-07-22 9:58 Barbier, Renaud (GE Infrastructure)
@ 2004-07-22 11:47 ` Gerhard Jaeger
0 siblings, 0 replies; 6+ messages in thread
From: Gerhard Jaeger @ 2004-07-22 11:47 UTC (permalink / raw)
To: linuxppc-embedded
Hi,
checkout
arch/ppc/mm/pgtable.c
there you'll find the ioremap function which is used to remap physical
addresses. This function calls internaly fixup_big_physaddr(), defined in
arch/ppc/kernel/ibm44x_common.c
This fixup_big_physaddr() adjusts some 32bit addresses to some corresponding
36bit addresses, which can be mapped by the kernel by calling ioremap64.
Your example:
Calling mmap with the address 0x80002000 (see also include/asm-ppc/ibm44x.h)
will map the PCI area, by trapping this 0x80002000 and making a 36bit address
out of it. There a 3 "trap" areas defined:
/*
* 36-bit trap ranges
*/
#define PPC44x_IO_LO 0x40000000
#define PPC44x_IO_HI 0x40001000
#define PPC44x_PCICFG_LO 0x0ec00000
#define PPC44x_PCICFG_HI 0x0ec7ffff
#define PPC44x_PCIMEM_LO 0x80002000
#define PPC44x_PCIMEM_HI 0xffffffff
Hope this helps,
Gerhard
On Thursday 22 July 2004 11:58, Barbier, Renaud (GE Infrastructure) wrote:
> As you know the PCI address(and other embedded device) are seen through a
> 36-bit address space.
>
> How do you map this address from user space?
>
> I have seen a message from 2002 saying it is not supported. Anything new
> since then?
>
> thanks.
--
Gerhard Jaeger g.jaeger@sysgo.com
SYSGO AG Embedded and Real-Time Software
Voice: + 49 731 94683-0 Fax: + 49 731 94683-10
www.sysgo.com | www.elinos.com | www.osek.de | www.imerva.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-07-27 20:29 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-07-27 18:20 440GX: mapping PCI address Barbier, Renaud (GE Infrastructure)
2004-07-27 20:29 ` Matt Porter
-- strict thread matches above, loose matches on Subject: below --
2004-07-22 14:43 Barbier, Renaud (GE Infrastructure)
2004-07-22 16:20 ` Matt Porter
2004-07-22 9:58 Barbier, Renaud (GE Infrastructure)
2004-07-22 11:47 ` Gerhard Jaeger
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).