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:44:05 +0530 [thread overview]
Message-ID: <3700cfbb0159d56cecbda0e06a2957e3@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1010011558290.22941@utopia.booyaka.com>
Paul Walmsley wrote:
> On Sat, 2 Oct 2010, Anand Gadiyar wrote:
>
> > 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.
>
> We had linux-omap booting on the 3430SDP ES1.0 from at least 2007:
>
>
http://linux.omap.com/pipermail/linux-omap-open-source/2007-November/01216
0.html
>
> We've used the 3430SDP ES1.0 as part of our regular testbed up until
last
> year, when it fried itself, so as far as I know, it's worked the whole
> time.
>
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).
- Anand
next prev parent reply other threads:[~2010-10-01 22:14 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 [this message]
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=3700cfbb0159d56cecbda0e06a2957e3@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.