From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot maintainers: some boards are broken by recent mach-type update
Date: Fri, 28 Oct 2011 23:10:08 +0200 [thread overview]
Message-ID: <201110282310.08437.marek.vasut@gmail.com> (raw)
In-Reply-To: <4EAAEDA9.2060504@aribaud.net>
Hi Albert,
> Hello all,
>
> Recently the ARM mach-types.h file has been brought in sync with its
> Linux original, leasing to a number of boards not being listed any more,
> as the new list only contains boards which have actual Linux support or
> were declared less than one year ago.
>
> The symptom is a build failure with a message of the form "error:
> 'MACH_TYPE_XXXXXX' undeclared (first use in this function)".
>
> U-Boot maintainers of such boards (in Cc: of this mail) should provide a
> patch to re-introduce the MACH_TYPE_XXXXXX definition in their boards'
> config header file in include/configs/.
>
> Note that three boards do not have a maintainer and will be removed if
> nobody steps forward to take over their maintainership. They have been
> listed below as ORPHAN, and since they are all PXA boards, I have CC:ed
> Marek just in case.
>
> Here is the list of broken boards (BTW: how about putting maintainer
> identity in boards.cfg, or at least turning MAINTAINERS into a format
> more easily parseable?)
>
> -------------------------
>
> Ajay Bhargav <ajay.bhargav@einfochips.com>
>
> gplugd ARM926EJS (ARMADA100 88AP168 SoC)
Ajay, you have warnings in your damn ethernet code !!! Have you ever tested it
?!
>
> Luca Ceresoli <luca.ceresoli@comelit.it>
>
> dig297 ARM ARMV7 (OMAP3530 SoC)
>
> Po-Yu Chuang <ratbert@faraday-tech.com>
>
> a320evb FA526 (ARM920T-like) (a320 SoC)
>
> Daniel Gorsulowski <daniel.gorsulowski@esd.eu>
>
> meesc ARM926EJS (AT91SAM9263 SoC)
> otc570 ARM926EJS (AT91SAM9263 SoC)
>
> Ilko Iliev <iliev@ronetix.at>
>
> PM9261 AT91SAM9261
> PM9263 AT91SAM9263
> PM9G45 ARM926EJS (AT91SAM9G45 SoC)
>
> Prakash Kumar <prakash@embedx.com>
>
> cerf250 xscale/pxa
Drop unless I get fixes from maintainer in a week or request for longer time to
fix.
>
> Valentin Longchamp <valentin.longchamp@keymile.com>
>
> km_kirkwood ARM926EJS (Kirkwood SoC)
> portl2 ARM926EJS (Kirkwood SoC)
>
> David M?ller <d.mueller@elsoft.ch>
>
> VCMA9 ARM920T
>
> Jens Scharsig <esw@bus-elektronik.de>
>
> eb_cpux9k2 ARM920T (AT91RM9200 SoC)
>
> Heiko Schocher <hs@denx.de>
>
> mgcoge3un ARM926EJS (Kirkwood SoC)
>
> Robert Schwebel <r.schwebel@pengutronix.de>
>
> csb226 xscale/pxa
> innokom xscale/pxa
Drop unless I get fixes from maintainer in a week or request for longer time to
fix. (here I have some feeling it's not gonna be fixed)
>
> Albin Tonnerre <albin.tonnerre@free-electrons.com>
>
> sbc35_a9g20 ARM926EJS (AT91SAM9G20 SoC)
> tny_a9260 ARM926EJS (AT91SAM9260 SoC)
> tny_a9g20 ARM926EJS (AT91SAM9G20 SoC)
>
> Matthias Weisser <weisserm@arcor.de>
>
> jadecpu ARM926EJS (MB86R01 SoC)
>
> ORPHAN:
>
> cradle xscale/pxa
> pleb2 xscale/pxa
> xm250 xscale/pxa
Drop, sorry.
Cheers
next prev parent reply other threads:[~2011-10-28 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 18:00 [U-Boot] U-Boot maintainers: some boards are broken by recent mach-type update Albert ARIBAUD
2011-10-28 21:10 ` Marek Vasut [this message]
2011-10-28 21:22 ` Robert Schwebel
2011-10-28 23:18 ` Mike Frysinger
2011-10-28 23:20 ` Mike Frysinger
2011-11-05 8:25 ` "David Müller (ELSOFT AG)"
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201110282310.08437.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox