From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, Felipe Balbi <balbi@ti.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Luciano Coelho <coelho@ti.com>, Roger Quadros <rogerq@ti.com>,
linux-arm-kernel@lists.infradead.org,
Kishon Vijay Abraham I <kishon@ti.com>,
Ravi Babu <ravibabu@ti.com>,
Ruslan Bilovol <ruslan.bilovol@ti.com>
Subject: Re: Multiple issues with omap4 panda es in linux next
Date: Fri, 19 Apr 2013 23:11:06 +0530 [thread overview]
Message-ID: <517181B2.9070302@ti.com> (raw)
In-Reply-To: <20130419171318.GK10155@atomide.com>
On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote:
> Hi all,
>
> Here's a list of breakage I've noticed so far while trying to
> use linux next on my pandaboard es. Probably similar issues exist
> on other boards as well.
>
> Ideally we would not have any breakage by the merge window, so
> let's try to get these fixed ASAP:
>
> 1. Serial console broken on panda es booting with DT
>
> The symptoms are dmesg output stopping after few lines
> and only continuing after pressing a key. Does not seem to
> happen on blaze with DT for some reason. And does not happen
> on panda es with legacy booting.
>
This one is known and reported on list along with fix patches and
later pull request [1].
Unfortunately with all the testing and everything and patches have
been on the list for quite some time, feedback on one of the patch
received was after pull request and then there was no further
clarification. That series address the same exact issue you have
mentioned above.
Regards,
Santosh
[1] http://patchwork.ozlabs.org/patch/229269/
next prev parent reply other threads:[~2013-04-19 17:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 17:13 Multiple issues with omap4 panda es in linux next Tony Lindgren
2013-04-19 17:41 ` Santosh Shilimkar [this message]
2013-04-19 17:44 ` Tony Lindgren
2013-04-19 17:53 ` Santosh Shilimkar
2013-04-19 18:18 ` Tony Lindgren
2013-04-25 13:58 ` Kevin Hilman
2013-04-26 8:40 ` Santosh Shilimkar
2013-04-22 7:49 ` Felipe Balbi
2013-04-22 8:41 ` Kishon Vijay Abraham I
2013-04-22 18:03 ` Tony Lindgren
2013-04-23 15:10 ` Kishon Vijay Abraham I
2013-04-23 17:23 ` Tony Lindgren
2013-04-23 21:31 ` Tony Lindgren
2013-04-23 23:16 ` Tony Lindgren
2013-04-24 5:41 ` Kishon Vijay Abraham I
2013-04-24 19:08 ` Tony Lindgren
2013-04-24 19:23 ` Tony Lindgren
2013-04-25 9:04 ` Felipe Balbi
2013-04-25 15:01 ` Tony Lindgren
2013-04-25 15:13 ` Felipe Balbi
2013-04-22 9:08 ` Tomi Valkeinen
2013-04-22 10:24 ` Tomi Valkeinen
2013-04-22 12:21 ` Grygorii Strashko
2013-04-22 18:08 ` Tony Lindgren
2013-04-23 13:53 ` Grygorii Strashko
2013-04-23 17:31 ` Tony Lindgren
2013-04-24 19:44 ` Tony Lindgren
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=517181B2.9070302@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=balbi@ti.com \
--cc=coelho@ti.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=ravibabu@ti.com \
--cc=rogerq@ti.com \
--cc=ruslan.bilovol@ti.com \
--cc=tomi.valkeinen@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).