From: Mark Salter <msalter@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PULL] Add support for Texas Instruments C6X architecture
Date: Sun, 06 Nov 2011 15:05:27 -0500 [thread overview]
Message-ID: <1320609928.2382.12.camel@deneb.redhat.com> (raw)
In-Reply-To: <CA+55aFwodK9Z7cUu4bdhmOcR2L3R_fBYdTyJv6iQKcYFrH2Xew@mail.gmail.com>
On Sun, 2011-11-06 at 11:07 -0800, Linus Torvalds wrote:
> >
> > I think the best counter argument is that it leads to paddr != vaddr
> > in the case of NOMMU with a non-zero memory base. My view is that in
> > all NOMMU cases, physical and virtual addresses should be the same.
> > Otherwise, you end up breaking drivers which need to pass physical
> > addresses to devices.
>
> That's a totally insane argument.
Not *totally* insane. Forget the last sentence. You're right that its a
driver problem. Creating a physical address space separate from the
"virtual" space on a NOMMU arch where the hw uses a one-to-one mapping
seems a long way to go. My point here is that the simplest NOMMU case is
paddr == vaddr. Right now, the generic headers are broken in that regard
for hardware that maps RAM at a non-zero address.
So, okay. Let's have some more discussion among more people. There is
certainly more than one approach to fix the currently broken bits and I
sure don't claim to have the one true way. I just want to do what needs
to be done to make the port acceptable for upstream inclusion.
--Mark
next prev parent reply other threads:[~2011-11-06 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 20:27 [PULL] Add support for Texas Instruments C6X architecture Mark Salter
2011-11-05 1:23 ` Linus Torvalds
2011-11-05 21:39 ` Mark Salter
2011-11-05 22:38 ` Linus Torvalds
2011-11-06 15:24 ` Mark Salter
2011-11-06 19:07 ` Linus Torvalds
2011-11-06 20:05 ` Mark Salter [this message]
2011-11-08 18:08 ` Mark Salter
2011-11-08 19:03 ` Linus Torvalds
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=1320609928.2382.12.camel@deneb.redhat.com \
--to=msalter@redhat.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.