From: Cory Maccarrone <darkstar6262@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, miknix@gmail.com,
a.j.buxton@gmail.com, linwizard-devel@lists.sf.net
Subject: Re: Commit 0c8219f0... breaks omap7xx support
Date: Fri, 28 May 2010 21:01:01 -0700 [thread overview]
Message-ID: <AANLkTini1wjhRXEfW4AjSdkVEYGpYXpuLcct-1l4pq0o@mail.gmail.com> (raw)
In-Reply-To: <20100315182939.GV2900@atomide.com>
On Mon, Mar 15, 2010 at 11:29 AM, Tony Lindgren <tony@atomide.com> wrote:
>
> * Cory Maccarrone <darkstar6262@gmail.com> [100309 15:38]:
> > On Tue, Mar 9, 2010 at 7:56 AM, Tony Lindgren <tony@atomide.com> wrote:
> > >
> > > Does your system boot without any patches if DEBUG_LL is not set
> > > in your .config?
> >
> > No, it doesn't. Seems like the debugging code is still trying to run,
> > even disabled. If I add in that check, it'll boot with DEBUG_LL not
> > set, but won't without that.
>
> Sorry for the delay on this. How about with the following patch with
> DEBUG_LL not set?
>
> Note that this is using the shift register now too.
>
> Regards,
>
> Tony
Sorry I took so long on this one. This patch worked beautifully for
me on the latest kernel tree. Any chance of it getting in for one of
the RCs of this next kernel?
Thanks
- Cory
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-05-29 4:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 4:56 Commit 0c8219f0... breaks omap7xx support Cory Maccarrone
2010-03-09 0:48 ` Tony Lindgren
2010-03-09 1:51 ` Cory Maccarrone
2010-03-09 2:46 ` Tony Lindgren
2010-03-09 3:06 ` Cory Maccarrone
2010-03-09 15:56 ` Tony Lindgren
2010-03-09 23:41 ` Cory Maccarrone
2010-03-15 18:29 ` Tony Lindgren
2010-03-15 19:08 ` Tony Lindgren
2010-05-29 4:01 ` Cory Maccarrone [this message]
2010-05-31 8:21 ` 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=AANLkTini1wjhRXEfW4AjSdkVEYGpYXpuLcct-1l4pq0o@mail.gmail.com \
--to=darkstar6262@gmail.com \
--cc=a.j.buxton@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=linwizard-devel@lists.sf.net \
--cc=miknix@gmail.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.