[U-Boot] [STATUS] WARNING: huge ARM board removal pending

Graeme Russ
2011-06-03T11:09:49Z

On 03/06/11 07:51, Wolfgang Denk wrote:
>
> Hi,
>
> this is a * W A R N I N G * message to maintainers / users / owners
> of ARM boards. If your board fails to build in the current release,
> it will be subject to a big cleanup action which is going to remove
> all old, unmaintained and broken boards in the next merge window.
> According to our current schedule, this is in 10 days from now.
>
>
> At present, the following 112 boards are scheduled for removal:
>
> B2 at91sam9m10g45ek edb9307a omap2420h4
> CPU9260 at91sam9rlek edb9312 omap5912osk
> CPU9G20 cmc_pu2 edb9315 omap730p2
> CPUAT91 cp1026 edb9315a otc570_dataflash
> SBC35_A9G20 cp1136 ep7312 pm9261
> SMN42 cp920t evb4510 pm9263
> TNY_A9260 cp922_XA10 gcplus pm9g45
> TNY_A9G20 cp926ejs impa7 sbc2410x
> afeb9260 cp946es imx31_phycore scb9328
> ap7 cp966 imx31_phycore_eet shannon
> ap720t cpu9260 integratorap smdk2400
> ap920t cpu9260_128M integratorcp smdk6400
> ap922_XA10 cpu9260_nand jornada snapper9260
> ap926ejs cpu9260_nand_128M kb9202 snapper9g20
> ap946es cpu9G20 lart spear300
> ap966 cpu9G20_128M lpc2292sodimm spear310
> apollon cpu9G20_nand lpd7a400 spear320
> armadillo cpu9G20_nand_128M m501sk spear600
> assabet cpuat91 meesc tnetv107x_evm
> at91cap9adk cpuat91_ram meesc_dataflash top9000eval_xe
> at91rm9200dk csb226 modnet50 top9000su_xe
> at91rm9200ek csb637 mx1ads trab
> at91rm9200ek_ram dnp1110 mx1fs2 versatile
> at91sam9260ek eb_cpux9k2 mx31ads versatileab
> at91sam9261ek edb9301 netstar versatilepb
> at91sam9263ek edb9302 omap1510inn voiceblue
> at91sam9g10ek edb9302a omap1610h2 zipitz2
> at91sam9g20ek edb9307 omap1610inn zylonite
>
>
> Please submit fixes to prevent removal.
>
> Note: countdown is T minus 10 days, and counting.
>
> You have been warned.
>

Looks like the worst offenders of the current timer API are also on this
list. If they get fixed within the next merge window, the timer API will
get updated 'for free' - If you bring them back from the dead, you will
have to sort out updating timer API usage yourself (as well as relocation)

Regards,

Graeme