From: pascal@pabr.org
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [RFC] Support 36-bit iomem on 32-bit Au1x00
Date: Tue, 26 Jan 2010 22:19:22 +0100 [thread overview]
Message-ID: <i8xpr4wftsy.fsf@pabr.org> (raw)
In-Reply-To: <f861ec6f1001261246y545e7a9ahe11eaf16fd587959@mail.gmail.com>
Manuel Lauss writes:
> Have you tried to register a platform device above the 4G line? I get an oops
> inside the platform device match code when I do. I'll try to figure out why.
Yes, I used these patches on top of 2.6.33-rc2 and 2.6.33-rc2-next-20100101
for an ethernet chip at 0xd:1000:0000 on a Au1250 board.
I don't remember seeing oopses while I was figuring out how to get
36-bit I/O working. arch/x86 and arch/powerpc have been supporting
32-bit processors with 64-bit physical addresses for a long time,
so I would expect the generic resource management code to be reliable.
There are other changes in my tree, but I can't think of anything
which might affect this. Let me know if I can help further.
Pascal
next prev parent reply other threads:[~2010-01-26 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-03 12:39 [RFC] Support 36-bit iomem on 32-bit Au1x00 pascal
2010-01-26 20:46 ` Manuel Lauss
2010-01-26 21:19 ` pascal [this message]
2010-01-28 13:18 ` Ralf Baechle
2010-01-28 13:22 ` Manuel Lauss
2010-01-28 13:53 ` 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=i8xpr4wftsy.fsf@pabr.org \
--to=pascal@pabr.org \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@googlemail.com \
/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.