| 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
| ||
|
Date: Thu, 7 Apr 2011 22:44:57 +0100 From: Alexander Clouter <alex@...riz.org.uk> To: Alexander Holler <holler@...oftware.de> Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org Subject: Re: [PATCH 1/2] ARM: Differentiate SheevaPlugs and DockStars on the basis of the memory size. * Alexander Holler <holler@...oftware.de> [2011-04-07 23:31:08+0200]: > > Requiring a machine ID and the needed stuff to handle that for a > board which just is using two GPIOs different than another board is > why the ARM tree exploded. And requiring a machine ID just to follow > the rule that a machine ID is much better than some pretty unique hw > feature is in my humble opinion senseless and that the resulting code > is more readable and better to maintain is a myth. > It's something that most people agree with you on too. However, I am guessing it's around as no one else *at the time* of it's conception could think of a better way. Now this is why there is a lot of work being done on device-tree. > Sorry that I wanted to help there. Will not try it again. > Yeah, as obviously no tries to help anyone improve around here: http://groups.google.com/group/openrd/browse_frm/thread/7ba48f2d7916a88f/2b89c877c4f39098?tvc=1&fwc=1 http://lists.infradead.org/pipermail/linux-arm-kernel/2010-August/022855.html http://lists.infradead.org/pipermail/linux-arm-kernel/2010-August/024072.html http://git.kernel.org/?p=linux/kernel/git/nico/orion.git;a=commit;h=f2ac38dc Regards -- Alexander Clouter .sigmonster says: Graduate life: It's not just a job. It's an indenture. -- 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