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: Fri, 07 Jun 2013 12:26:57 +0200 From: Henrik Nordström <henrik@...riknordstrom.net> To: "luke.leighton" <luke.leighton@...il.com> Cc: Linux on small ARM machines <arm-netbook@...ts.phcomp.co.uk>, Russell King - ARM Linux <linux@....linux.org.uk>, devicetree-discuss <devicetree-discuss@...abs.org>, Stephen Warren <swarren@...dotorg.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Tomasz Figa <tomasz.figa@...il.com>, debian-arm@...ts.debian.org, "jonsmirl@...il.com" <jonsmirl@...il.com>, linux-arm-kernel@...ts.infradead.org, debian-kernel@...ts.debian.org Subject: Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1)) fre 2013-06-07 klockan 09:02 +0100 skrev luke.leighton: > ok. so. we come back to the question again: what shall i propose to > them that they consider doing, and what benefit would it be to them to > do so? Just tell them that the kernel is moving to a different configuration syntax called Device Tree, but apart from updating kernel drivers to the new way of configuring things it only have minor impact on their envionment. It is still possible to use the fex file for all board configuration details, only requires a small tool for translating fex to device tree. The change only impacts kernel, and a small change to their SDK build scripts to also build the device tree from the fex. It is no big deal really in structural terms. There is far bigger structural changes in the kernel which coincides with this and will require some developer time to adjust for. Had they upstreamed their changes earlier then... Regards Henrik -- 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