| 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
| ||
|
Message-ID: <50D2AD59.8070901@nvidia.com> Date: Thu, 20 Dec 2012 11:46:57 +0530 From: Laxman Dewangan <ldewangan@...dia.com> To: Stephen Warren <swarren@...dotorg.org> CC: "linux@....linux.org.uk" <linux@....linux.org.uk>, "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] ARM: tegra30: tegra30 gpio is not compatible with tegra20 gpio On Wednesday 19 December 2012 10:34 PM, Stephen Warren wrote: > On 12/19/2012 07:57 AM, Laxman Dewangan wrote: >> tegra30 gpio controller is not compatible with the tegra20 due to >> their bank stride i.e. Tegra20 bank stride is 0x80 where Tegra30 >> bank stride is 0x100. > Thanks, I've been meaning to clean this up for a while, but never got > around to it. I can apply after the merge window is closed; I don't > think it's important enough to warrant going into 3.8 or earlier, since > it doesn't cause any active problems. > > Have you checked all the other devices to make sure they're all correct to? Not yet, I am going one by one for finding if anything we are missing on IO drivers or not and then came across this. -- 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/
Powered by blists - more mailing lists