linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: vexpress: add debug UARTs to DEBUG_LL kconfig choice
Date: Thu, 5 Jul 2012 10:33:48 +0100	[thread overview]
Message-ID: <20120705093348.GA3399@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1341480232.1173.22.camel@hornet>

Hi Pawel,

On Thu, Jul 05, 2012 at 10:23:52AM +0100, Pawel Moll wrote:
> On Wed, 2012-07-04 at 16:01 +0100, Will Deacon wrote:
> > This patch avoids probing the various possible UART locations on the
> > different Versatile Express motherboards and instead adds entries into
> > the DEBUG_LL kconfig choice for the two possible memory maps.
> 
> I wrote similar thing (keeping the autodetection as one of the options)
> some time ago, but Russell didn't like it (because it wasn't DEBUG_LL
> choice) and I didn't have time to rework it for 3.5 merge window. Will
> get this out this time.

Ok, thanks. We have similar code in mach/uncompress.h -- how do you feel
about using the same approach there? I've seen the decompressor explode due
to the mrc and it's a royal pain to track down.

Will

  reply	other threads:[~2012-07-05  9:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-04 15:01 [PATCH 1/2] ARM: vexpress: add debug UARTs to DEBUG_LL kconfig choice Will Deacon
2012-07-04 15:01 ` [PATCH 2/2] ARM: vexpress: remove automatic errata workaround selection Will Deacon
2012-07-05  9:25   ` Pawel Moll
2012-07-05  9:23 ` [PATCH 1/2] ARM: vexpress: add debug UARTs to DEBUG_LL kconfig choice Pawel Moll
2012-07-05  9:33   ` Will Deacon [this message]
2012-07-05  9:38     ` Pawel Moll
2012-07-05  9:42       ` Will Deacon
2012-07-06 13:25         ` Will Deacon
2012-07-08 16:00           ` Will Deacon

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=20120705093348.GA3399@mudshark.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).