linux-kernel - Re: [PULL] Add support for Texas Instruments C6X architecture

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CA+55aFx_bjbpbY8wG11UqVmnK_-hNJBQTM_OhAAMjDyEyvbtUg@mail.gmail.com>
Date:	Tue, 8 Nov 2011 11:03:45 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Mark Salter <msalter@...hat.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	"JACQUIOT-XID, Aurelien" <a-jacquiot@...com>,
	Arnd Bergmann <arnd@...db.de>
Subject: Re: [PULL] Add support for Texas Instruments C6X architecture

On Tue, Nov 8, 2011 at 10:08 AM, Mark Salter <msalter@...hat.com> wrote:
>
> Having a little time to think about this some more, I'm going to take
> another crack at it. Defining __pa/__va with PAGE_OFFSET as they are
> currently creates a physical space which doesn't match the hardware
> when PAGE_OFFSET is non-zero.
>
> For arches using device tree support, that means that the physical
> addresses in the device tree are either linux-specific or early boot
> code would have to go through the tree to fixup the "hardware physical"
> addresses so that they are "linux physical" addresses for the kernel.

Ok, that's actually a good argument - external interfaces defining
what "physical" means.

Fair enough. I'll consider myself convinced.

         Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/