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>] [day] [month] [year] [list]
Message-ID: <54104971.1080501@atmel.com>
Date:	Wed, 10 Sep 2014 14:52:01 +0200
From:	Nicolas Ferre <nicolas.ferre@...el.com>
To:	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
	ARM kernel <arm@...nel.org>
CC:	Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
	Boris BREZILLON <boris.brezillon@...e-electrons.com>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>,
	Ludovic Desroches <ludovic.desroches@...el.com>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	"Wu, Josh" <Josh.wu@...el.com>, voice <voice.shen@...el.com>,
	"Yang, Wenyou" <Wenyou.Yang@...el.com>
Subject: [ANNOUNCE] ARM: at91: removal of board files

Hi all,

The Atmel ARM-based SoC community (aka AT91) has been working on Device
Tree since early August 2011. I only come back on this long process just
for saying a big thank you to all people involved in this effort which
in the end gives to the AT91 community a cleaner, stronger and more
generic code base.

With the work about to being completed on the LCD controller we have now
a comprehensive support for all AT91 SoC in DT. Some drivers were
converted to DT several years ago, some have just been converted but we
can rely on this technology and stop having to maintain useless code.

So today, it's time for making one of the latest steps of this work: the
*removal* of old-style "board-*.c" and "at91*_devices.c" files in
mach-at91 directory.

A work has been started several months ago (Cf. ARM: at91: DT: switch C
board to DT, on Nov. 2013) but we didn't have much feedback from board
maintainers.
This time, we will simply remove the support for the boards that have
not migrated to the Device Tree by the 3.18-3.19 time frame. To ensure
this does not happen to your board, make sure to:
- rework the patches sent by Jean-Christophe back then
- or send your own .dts file for your board.
All in all it will be easy to build these .dts files both from existing
boards with the same SoC or convert the old board files that could
easily be found in git history.

BTW: Let me recall some simple rules while submitting an AT91 board DT file:
- prefix .dts file name with "at91-"
  (at91-foxg20.dts or at91-sama5d3_xplained.dts for instance)
- DT nodes in address ascending order
- command line without "mem" parameter and as short and generic
  as possible
- sorted inclusion of the .dts file in arch/arm/boot/dts/Makefile
- a vendor used in a DT file must be added in
  Documentation/devicetree/bindings/vendor-prefixes.txt as well
- consider using the dual license approach for your board .dts file:
  GPLv2+ and X11:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/283767.html

Please do not hesitate to contact the AT91 community for any question: I
know that you may have difficulties to switch to this method if you are
not used to kernel development, definitively, we can help.

Best regards,
-- 
Nicolas Ferre
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ