From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: Kevin Hilman <khilman@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Javier Martinez Canillas <javier@dowhile0.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Subject: Re: regressions in linux-next?
Date: Thu, 24 Apr 2014 08:40:31 -0700 [thread overview]
Message-ID: <20140424154031.GA22987@atomide.com> (raw)
In-Reply-To: <CAGo_u6r79StfHwf8t8OB5vyhByfusi3EF=PZA186piiAci_wjw@mail.gmail.com>
* Nishanth Menon <nm@ti.com> [140424 08:25]:
> On Thu, Apr 24, 2014 at 10:16 AM, Kevin Hilman <khilman@linaro.org> wrote:
> > Linus Walleij <linus.walleij@linaro.org> writes:
> >
> >> On Tue, Apr 22, 2014 at 5:52 PM, Javier Martinez Canillas
> >> <javier@dowhile0.org> wrote:
> >>
> >>> I've revised the patch again and I couldn't find the reason why
> >>> certain boards are failing to boot.
> >>>
> >>> I can't reproduce this issue since I only have a DM3730 IGEPv2 board
> >>> which boots fine but I should have access to an AM3354 IGEP Aquila
> >>> board which is similar to the am335x-evmsk so I may be able to debug
> >>> it.
> >>
> >> It would really REALLY appreciate if some of the people maintaining
> >> and using OMAP1 would help Javier out in this refactoring operation.
> >>
> >> I'd really *hate* to have to drop his patches because of a lack of
> >> boards. This refactoring is necessary to handle the exploding
> >> multitude of GPIO drivers moving forward.
> >>
> >> We even tried to get an Innovator to boot just to be able to refactor
> >> OMAP stuff but fell short on some special JTAG reflash snag so
> >> we are dependent on maintainers to help out here :-/
> >
> > Unfortunately, my OMAP1 (omap5912/OSK[1]) died last year and I haven't been
> > able to get it booting again. I wonder if Spectrum Digital still has
> > these available? Their websites[1] says "call for price."
> >
> > Kevin
> >
> > [1] http://www.spectrumdigital.com/product_info.php?products_id=39
>
>
> Perhaps dumb question: but are there folks who really care about omap1
> boot anymore in upstream? should it be time to deprecate it - say for
> 3.17 or so?
Why? There are people still using omap1 and it works just fine. And
in general the maintenance work needed for omap1 is really minimal.
And in the GPIO case the issue was also discovered on new TI boards.
Regards,
Tony
next prev parent reply other threads:[~2014-04-24 15:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 13:18 regressions in linux-next? Nishanth Menon
2014-04-22 13:29 ` Peter Ujfalusi
2014-04-22 15:52 ` Javier Martinez Canillas
2014-04-22 19:37 ` Ezequiel Garcia
2014-04-22 22:32 ` Javier Martinez Canillas
2014-04-22 22:00 ` Linus Walleij
2014-04-22 23:03 ` Javier Martinez Canillas
2014-04-22 23:47 ` Tony Lindgren
2014-04-24 15:16 ` Kevin Hilman
2014-04-24 15:25 ` Nishanth Menon
2014-04-24 15:37 ` Javier Martinez Canillas
2014-04-24 15:42 ` Tony Lindgren
2014-04-24 16:33 ` Javier Martinez Canillas
2014-04-24 16:47 ` Tony Lindgren
2014-04-24 15:40 ` Tony Lindgren [this message]
2014-04-24 15:46 ` Nishanth Menon
2014-04-24 16:17 ` Tony Lindgren
2014-04-24 17:08 ` Nishanth Menon
2014-04-24 19:59 ` Aaro Koskinen
2014-04-24 19:22 ` Aaro Koskinen
2014-04-28 22:04 ` Paul Walmsley
2014-04-22 15:13 ` Nishanth Menon
2014-04-22 21:57 ` Nishanth Menon
2014-04-22 22:45 ` Javier Martinez Canillas
2014-04-22 22:52 ` Nishanth Menon
2014-04-22 23:08 ` Javier Martinez Canillas
2014-04-23 1:30 ` Nishanth Menon
2014-04-23 7:24 ` Javier Martinez Canillas
2014-04-23 10:59 ` Peter Ujfalusi
2014-04-23 13:01 ` Linus Walleij
2014-04-23 13:29 ` Nishanth Menon
2014-04-23 14:38 ` Linus Walleij
2014-04-23 14:50 ` Javier Martinez Canillas
2014-04-23 14:52 ` Linus Walleij
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=20140424154031.GA22987@atomide.com \
--to=tony@atomide.com \
--cc=javier.martinez@collabora.co.uk \
--cc=javier@dowhile0.org \
--cc=khilman@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=santosh.shilimkar@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox