From: Tony Lindgren <tony@atomide.com>
To: Anand Gadiyar <gadiyar@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Dropping omap3430 ES1.0 support in mainline
Date: Fri, 1 Oct 2010 14:58:32 -0700 [thread overview]
Message-ID: <20101001215832.GC3117@atomide.com> (raw)
In-Reply-To: <d0443bbf588bf1e8a7efbd0014816753@mail.gmail.com>
* Anand Gadiyar <gadiyar@ti.com> [101001 14:38]:
> Tony, all,
>
> The OMAP3430 ES1.0 was pretty much a test chip, with the only known board
> being the 3430ES1.0 SDP. There are only a small number of these boards
> outside TI and within TI, they've likely never been used in over 2 years.
> It's unlikely that these boards still work on mainline, and likely have
> been broken in linux-omap since the very beginning.
>
> Between ES1.0 and ES2.0 we've had several major changes in the clock
> nodes,
> and IPs. However we're still keeping code/data on these in the kernel
> today.
>
> Since all later OMAP3 chips have been very similar to ES2.0, it probably
> makes sense to drop support for the ES1.0. This would result in a small
> but probably significant reduction in the current code. If you're okay
> with dropping this support, we can slowly start working on this.
>
> What do you think?
No thanks!
Tony
next prev parent reply other threads:[~2010-10-01 21:58 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 [this message]
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
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=20101001215832.GC3117@atomide.com \
--to=tony@atomide.com \
--cc=gadiyar@ti.com \
--cc=linux-omap@vger.kernel.org \
/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.