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: Mon, 01 Dec 2008 13:08:31 +0200	[thread overview]
Message-ID: <4933C5AF.5040406@embedded-sol.com> (raw)
In-Reply-To: <1228118085.7356.115.camel@pasglop>

Benjamin Herrenschmidt wrote:
> On Mon, 2008-11-03 at 23:09 +0200, Felix Radensky wrote:
>   
>> Hi,
>>
>> I'm currently struggling with some application
>> that tries to access PCI-E memory by mmaping
>> address found in /sys/bus/pci/devices/<device>/resource
>>
>> mmap() fails with "invalid argument" error, apparently
>> because on 460EX PCI addresses are 36-bit.
>>
>> What is the correct way of accessing PCI-E from
>> userspace on this platform.
>>     
>
> I fixed a lot of these problems recently. Can you try again with
> 2.6.28-latest-rc ?
>   

Thanks a lot for this input.
The problem is that I have a custom board with quite a few kernel 
modifications,
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 ?

> Cheers,
> Ben.
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>   

  reply	other threads:[~2008-12-01 11:08 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 [this message]
2008-12-01 21:04     ` Benjamin Herrenschmidt
2008-12-02 22:38       ` Felix Radensky
2008-12-04  9:22         ` Felix Radensky

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=4933C5AF.5040406@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.