All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anand Gadiyar <gadiyar@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>
Subject: RE: Dropping omap3430 ES1.0 support in mainline
Date: Sat, 2 Oct 2010 03:58:13 +0530	[thread overview]
Message-ID: <cf484f0b347742791af6d563efefaeb4@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1010011615560.22941@utopia.booyaka.com>

Paul Walmsley wrote:
> On Sat, 2 Oct 2010, Anand Gadiyar wrote:
>
> > Okay, so we're aligned that you guys don't have an ES1 board to test,
> > and TI doesn't have any either. :)
> >
> > I'd still like to know if anyone in the wild still cares about the
board.
> >
> > (I see Tony already said "No thanks", but I'd like to know anyway).
>
> Why would we want to remove support for a board that should work fine
with
> linux-omap and isn't causing any problems with existing code?

I'm not sure it works fine, and if there are no users that care about
the board, then it would be nice to drop the support. If the board
works fine today, that's good, but has anyone tested the current
kernel on that board?

(we're struggling to keep linux-omap working on boards available now,
why support something that nobody cares about. It's not like I'm asking
3430 support to be dropped)

- the ES1 chip has never been available to the outside world beyond
sampling quantities
- no new developments are likely to happen on that board
- nobody's likely to have one of these around and care to boot it up
- there are plenty of replacements like the beagles which are lower
  cost, easier to obtain, and can beat an ES1 in speed

I'm okay having support for the board if someone's actually using it.
It's not such a big deal. It was just a thought - it came up because
Manju was looking at old errata docs, and came across something that
was specific to an ES1, but we realized there was no way to test it.

- Anand

  reply	other threads:[~2010-10-01 22:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01 21:46 Dropping omap3430 ES1.0 support in mainline Anand Gadiyar
2010-10-01 21:58 ` Tony Lindgren
2010-10-04  7:03   ` Felipe Balbi
2010-10-01 22:07 ` Paul Walmsley
2010-10-01 22:14   ` Anand Gadiyar
2010-10-01 22:16     ` Paul Walmsley
2010-10-01 22:28       ` Anand Gadiyar [this message]
2010-10-01 22:37         ` Paul Walmsley
2010-10-04  9:37         ` Cousson, Benoit

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=cf484f0b347742791af6d563efefaeb4@mail.gmail.com \
    --to=gadiyar@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=tony@atomide.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.