All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Radensky <felix@embedded-sol.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Accessing PCI-E resources on 460EX
Date: Thu, 04 Dec 2008 11:22:11 +0200	[thread overview]
Message-ID: <4937A143.2020100@embedded-sol.com> (raw)
In-Reply-To: <4935B900.5020405@embedded-sol.com>

Hi, Ben

Sorry for confusion. With 2.6.28-rc6 mmap() of resource0  works fine.
The application still doesn't work, but that's because it's not reading what
it expects from resource file. I guess it's no longer a kernel problem.

Thanks a lot for your help.

Felix.

Felix Radensky wrote:
> Benjamin Herrenschmidt wrote:
>> On Mon, 2008-12-01 at 13:08 +0200, Felix Radensky wrote:
>>  
>>> and I'm afraid it can take me some time to move from 2.6.26 to 2.6.28.
>>> Any chance I can backport you modifications to 2.6.26 ? Have you
>>> modified
>>> other files except arch/powerpc/sysdev/ppc4xx_pci.c to fix these
>>> problems ?
>>>
>>>     
>>
>> Yes, quite a few changes in the PCI layer etc...
>>
>> Board support changes shouldn't be too hard to port over tho, it depends
>> how you did them.
>>   
>
> I've managed to run 2.6.28-rc6 on this platform, it was not that 
> difficult after all.
> I only had to remove PCIX and PCIE0 from Canyonlands DTS, as they are not
> used on this board. However this did not solve my problem. Below are 
> relevant
> bits from dmesg
>
> PCIE1: Checking link...
> PCIE1: Device detected, waiting for link...
> PCIE1: link is up !
> PCI host bridge /plb/pciex@d20000000 (primary) ranges:
> MEM 0x0000000e80000000..0x0000000effffffff -> 0x0000000080000000
>  IO 0x0000000f80010000..0x0000000f8001ffff -> 0x0000000000000000
> 4xx PCI DMA offset set to 0x00000000
> PCIE1: successfully set as root-complex
> PCI: Probing PCI hardware
> PCI: Hiding 4xx host bridge resources 0000:80:00.0
> pci 0000:81:00.0: disabling ASPM on pre-1.1 PCIe device.  You can 
> enable it with 'pcie_aspm=force'
> pci 0000:80:00.0: PCI bridge, secondary bus 0000:81
> pci 0000:80:00.0:   IO window: disabled
> pci 0000:80:00.0:   MEM window: 0x80000000-0x800fffff
> pci 0000:80:00.0:   PREFETCH window: disabled
> bus: 80 index 0 io port: [0x00-0xffff]
> bus: 80 index 1 mmio: [0xe80000000-0xeffffffff]
> bus: 81 index 0 mmio: [0x0-0xfff]
> bus: 81 index 1 mmio: [0xe80000000-0xe800fffff]
> bus: 81 index 2 mmio: [0x0-0x0]
> bus: 81 index 3 mmio: [0x0-0x0]
>
> The application code that mmaps PCI memory is attached.
> The attempt to access /sys/bus/pci/devices/0000:81:00.0/resource0
> results in I/O error. The device in question is Mellanox Infiniband
> switch. I will gladly test any other ideas you may have.
>
> Felix.
>> Cheers,
>> Ben.
>>
>>
>> _______________________________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded@ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>   
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

      reply	other threads:[~2008-12-04  9:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03 21:09 Accessing PCI-E resources on 460EX Felix Radensky
2008-11-03 21:31 ` Ayman El-Khashab
2008-11-03 22:53   ` Felix Radensky
2008-11-04 18:40     ` Henry Bausley
2008-12-01  7:54 ` Benjamin Herrenschmidt
2008-12-01 11:08   ` Felix Radensky
2008-12-01 21:04     ` Benjamin Herrenschmidt
2008-12-02 22:38       ` Felix Radensky
2008-12-04  9:22         ` Felix Radensky [this message]

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=4937A143.2020100@embedded-sol.com \
    --to=felix@embedded-sol.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.