From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Andreas_Bie=DFmann?= Date: Wed, 01 Aug 2012 12:11:01 +0200 Subject: [U-Boot] [U-Boot-DM] List of offending drivers In-Reply-To: <201207270118.19524.marex@denx.de> References: <201207270118.19524.marex@denx.de> Message-ID: <501900B5.8000300@googlemail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Marek Vasut, On 27.07.12 01:18, Marek Vasut wrote: > Hello, > > Check the following list, it's the list of drivers scattered (misplaced) across > the tree. The list is not complete and might be inaccurate. But it should give a > good impression of what I'm going to break soon: > > board/atmel/at91rm9200ek/led.c > board/atmel/at91sam9260ek/led.c > board/atmel/at91sam9261ek/led.c > board/atmel/at91sam9263ek/led.c > board/atmel/at91sam9m10g45ek/led.c > board/atmel/at91sam9rlek/led.c these atmel specific led stuff is basically for very early debug (switching a LED after relocation, another one after board init, ..). It also provides possibility to use it in assembler code sections e.g. lowlevel_init. I do not really care about that cause I normally use JTAG to debug early code. The led switching at a specific stage could be done by one of the other generic led drivers. Beside that, I think for debugging early stage code without JTAG the serial line is much better than a LED which can only provide two states. Has anyone thought about that? Has anyone tried to add some 'early_printf' feature? Best regards Andreas Bie?mann