From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org,
"Santosh Shilimkar" <santosh.shilimkar@ti.com>,
"Cousson, Benoit" <b-cousson@ti.com>,
"Paul Walmsley" <paul@pwsan.com>, "Kevin Hilman" <khilman@ti.com>,
"Ohad Ben-Cohen" <ohad@wizery.com>,
"Afzal Mohammed" <afzal@ti.com>,
"Péter Ujfalusi" <peter.ujfalusi@ti.com>
Subject: Re: Errors at boot time from OMAP4430SDP (and a whinge about serial stuff)
Date: Fri, 12 Oct 2012 17:31:06 +0100 [thread overview]
Message-ID: <20121012163106.GP28061@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20121012162452.GD30339@atomide.com>
On Fri, Oct 12, 2012 at 09:24:52AM -0700, Tony Lindgren wrote:
> * Russell King - ARM Linux <linux@arm.linux.org.uk> [121012 08:56]:
> > As of today, I've rebased my serial changes as far forward as I dare at
> > the moment (to the commit before removal of DMA), and then merged it
> > into the latest trees from armsoc and myself, fixing up all the horrid
> > conflicts. I've finally got it to a stage where at least it compiles,
> > but unfortunately something has broken serial output from userspace
> > quite badly to the point that it doesn't work.
> >
> > I know that my serial changes were fine before I tried rebasing them (the
> > set I posted to the mailing list certainly did work) so I suspect that
> > it's down to incompatibilities between the fixes done by others (who didn't
> > really understand all issues involved) and those done by myself.
>
> Have you been able to locate the breaking patches, maybe those could
> be reverted?
Not yet; I'll look into it this weekend. I've only recently got stuff
back into a state where the kautobuild kernels don't error out during
the build for the OMAP and SA11x0 stuff. OMAP ended up in that
situation because of the duplicated serial efforts causing rather
disgusting and horrid conflicts.
next prev parent reply other threads:[~2012-10-12 16:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 15:54 Errors at boot time from OMAP4430SDP (and a whinge about serial stuff) Russell King - ARM Linux
2012-10-12 16:24 ` Tony Lindgren
2012-10-12 16:31 ` Russell King - ARM Linux [this message]
2012-10-12 16:34 ` Benoit Cousson
2012-10-12 16:56 ` Tony Lindgren
2012-10-12 18:47 ` Kevin Hilman
2012-10-14 18:30 ` Ohad Ben-Cohen
2012-10-16 18:10 ` Tony Lindgren
2012-10-16 18:26 ` Tony Lindgren
2012-10-17 9:10 ` Ohad Ben-Cohen
2012-10-17 12:43 ` Igor Grinberg
2012-10-18 16:58 ` Ohad Ben-Cohen
2012-10-19 17:07 ` Tony Lindgren
2012-10-21 14:54 ` Ohad Ben-Cohen
2012-10-23 7:37 ` Igor Grinberg
2012-10-23 7:51 ` Ohad Ben-Cohen
2012-10-23 9:46 ` Igor Grinberg
2012-10-24 1:54 ` Tony Lindgren
2012-10-24 11:15 ` Ohad Ben-Cohen
2012-10-25 19:03 ` Tony Lindgren
2012-10-15 5:54 ` Mohammed, Afzal
2012-10-16 18:12 ` Tony Lindgren
2012-10-16 19:24 ` Benoit Cousson
2012-10-16 19:53 ` Tony Lindgren
2012-10-15 7:37 ` Péter Ujfalusi
2012-10-23 10:10 ` Russell King - ARM Linux
2012-10-25 1:09 ` Tony Lindgren
2012-10-25 16:05 ` Balaji T K
2012-10-25 17:24 ` Kevin Hilman
2012-10-25 17:38 ` Kevin Hilman
2012-10-25 17:46 ` 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=20121012163106.GP28061@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=afzal@ti.com \
--cc=b-cousson@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=paul@pwsan.com \
--cc=peter.ujfalusi@ti.com \
--cc=santosh.shilimkar@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).