From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] omap1510inn/arm925t: maintain or remove?
Date: Sun, 11 Aug 2013 19:59:46 +0200 [thread overview]
Message-ID: <201308111959.46281.marex@denx.de> (raw)
In-Reply-To: <20130810130258.CEEC8380E09@gemini.denx.de>
Dear Wolfgang Denk,
> Dear Albert,
>
> In message <20130810084118.2d6c9804@lilith> you wrote:
> > Board omap1510inn is marked orphaned.
>
> ...
>
> > Should I try and clean this within my start.S commonalization effort
> > (first submission tonight, BTW) and move the signature generation
> > in ./Makefile as a new image rule, or should I simply remove omap1510inn
> > as well as the whole arm295t support?
> >
> > My own vote goes for removing; anyone wishing to resurrect the board
> > can do it from some commit before removal.
>
> My vote goes for removal, too. This is stuff which has long reached
> EOL.
I have one OMAP1510 board running U-Boot 1.1.3 (Palm Tungsten|T), but I dont
think I will ever touch it again, so my vote goes for removal too.
Best regards,
Marek Vasut
prev parent reply other threads:[~2013-08-11 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-10 6:41 [U-Boot] omap1510inn/arm925t: maintain or remove? Albert ARIBAUD
2013-08-10 13:02 ` Wolfgang Denk
2013-08-11 17:59 ` Marek Vasut [this message]
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=201308111959.46281.marex@denx.de \
--to=marex@denx.de \
--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