From: Will Deacon <will.deacon@arm.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
David Brown <davidb@codeaurora.org>
Subject: Re: [PATCHv2 2/2] ARM: debug: Move DEBUG_ICEDCC into the DEBUG_LL choice
Date: Thu, 29 Sep 2011 10:42:43 +0100 [thread overview]
Message-ID: <20110929094243.GC25061@e102144-lin.cambridge.arm.com> (raw)
In-Reply-To: <20110929092102.GB25061@e102144-lin.cambridge.arm.com>
On Thu, Sep 29, 2011 at 10:21:02AM +0100, Will Deacon wrote:
> On Thu, Sep 29, 2011 at 03:05:16AM +0100, Stephen Boyd wrote:
> > Chatting with David Brown made me realize that this patch now forces
> > ICEDCC for anybody who selects DEBUG_LL and hasn't moved to adding a
> > Kconfig in the choice menu. I'm not sure if that actually matters since
> > it may be incentive to put your machine of choice into this menu.
> >
> > Otherwise, we may want to drop this until a later point, or just leave
> > it out of the choice menu altogether.
>
> Given that the ICEDCC stuff shouldn't cause any other problems by having it
> enabled (that is, your kernel should still boot) then we should be alright
> leaving this as-is while platforms move over to the new scheme.
Bah, just took this for a spin on my Realview-PBX (Cortex-A9) platform and
the board won't boot unless I have a hardware debugger enabled that can
service the comms channel. This contradicts the Kconfig text which says:
It does include a timeout to ensure that the system does not
totally freeze when there is nothing connected to read.
so we certainly need to fix something!
Will
next prev parent reply other threads:[~2011-09-29 9:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 1:23 [PATCHv2 1/2] ARM: debug: Add UART1 config choices Stephen Boyd
2011-09-21 1:23 ` [PATCHv2 2/2] ARM: debug: Move DEBUG_ICEDCC into the DEBUG_LL choice Stephen Boyd
2011-09-21 7:56 ` Stephen Boyd
2011-09-29 2:05 ` Stephen Boyd
2011-09-29 9:21 ` Will Deacon
2011-09-29 9:42 ` Will Deacon [this message]
2011-09-29 9:46 ` Russell King - ARM Linux
2011-09-29 10:39 ` Will Deacon
2011-09-29 10:49 ` Russell King - ARM Linux
2011-09-29 17:22 ` Stephen Boyd
2011-09-29 17:30 ` Will Deacon
2011-09-29 18:04 ` David Brown
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=20110929094243.GC25061@e102144-lin.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=davidb@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=sboyd@codeaurora.org \
/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
all inboxes | Powered by JetHome®