| 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: <201011191253.58812.anarsoul@gmail.com> Date: Fri, 19 Nov 2010 12:53:58 +0200 From: Vasily Khoruzhick <anarsoul@...il.com> To: "Lars-Peter Clausen" <lars@...afoo.de> Cc: linux-arm-kernel@...ts.infradead.org, Kukjin Kim <kgene.kim@...sung.com>, Ben Dooks <ben-linux@...ff.org>, Marek Belisko <marek.belisko@...n-nandra.com>, linux-kernel@...r.kernel.org Subject: Re: [PATCH] ARM: s3x24xx: Fix gpiochip_add complaining. On Friday 19 November 2010 12:42:02 Lars-Peter Clausen wrote: > Hi > > Well it actually causes problems on systems with external gpio expanders, > because now the additional banks will take up the space which was meant > for the gpio expander chip and peripherals connected to it wont be > accessible. Ok, but it would be nice to see some runtime soc-type detection for gpiolib. s3c2410/s3c2440/s3c2442 doesn't differ too much (actually, they're same in gpiopart, s3c2410 lacks some gpiobanks that s3c244[0,2] have, and difference in pull-up/pull-down on s3c2440 and s3c2442). I think it's not good to make artificial restrictions for building single binary kernel for these socs. > I sent a patch[1] about this some time ago, but I guess it was never > applied... Try pinging Ben or Kukjin :) Regards Vasily -- 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