All of lore.kernel.org
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: fix DEBUG_UART_PHYS/VIRT issue when modifying DEBUG_LL output
Date: Wed, 17 Jun 2015 22:10:04 +0200	[thread overview]
Message-ID: <20150617221004.58699b2e@free-electrons.com> (raw)
In-Reply-To: <20150617194058.GZ7557@n2100.arm.linux.org.uk>

Russell,

On Wed, 17 Jun 2015 20:40:58 +0100, Russell King - ARM Linux wrote:

> > Russell, what do you think of the proposed approach?
> 
> I'd rather we killed all the defaults, rather than keep trying to fix
> these subtle issues.  That was always my goal of converting to this
> model anyway.
> 
> However, I think it's important not to loose this information (how many
> of us with lots of different platforms want to keep on digging through
> PDFs to try and find this documentation?)  I'd like to see a per-SoC
> file somewhere in Documentation/arm/ giving these details so at least
> they're relatively easy to find.

I personally find having the defaults for various popular platforms
readily available in menuconfig to be a lot easier than having to dig
some documentation to find the appropriate addresses.

I.e, the current way is perfect. It's just that there is no need to
show the physical/virtual addresses if an existing well-known platform
is selected, especially as it causes weird behavior due to how kconfig
works. Which Boris patch is solving.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

WARNING: multiple messages have this Message-ID (diff)
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Boris Brezillon <boris.brezillon@free-electrons.com>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: fix DEBUG_UART_PHYS/VIRT issue when modifying DEBUG_LL output
Date: Wed, 17 Jun 2015 22:10:04 +0200	[thread overview]
Message-ID: <20150617221004.58699b2e@free-electrons.com> (raw)
In-Reply-To: <20150617194058.GZ7557@n2100.arm.linux.org.uk>

Russell,

On Wed, 17 Jun 2015 20:40:58 +0100, Russell King - ARM Linux wrote:

> > Russell, what do you think of the proposed approach?
> 
> I'd rather we killed all the defaults, rather than keep trying to fix
> these subtle issues.  That was always my goal of converting to this
> model anyway.
> 
> However, I think it's important not to loose this information (how many
> of us with lots of different platforms want to keep on digging through
> PDFs to try and find this documentation?)  I'd like to see a per-SoC
> file somewhere in Documentation/arm/ giving these details so at least
> they're relatively easy to find.

I personally find having the defaults for various popular platforms
readily available in menuconfig to be a lot easier than having to dig
some documentation to find the appropriate addresses.

I.e, the current way is perfect. It's just that there is no need to
show the physical/virtual addresses if an existing well-known platform
is selected, especially as it causes weird behavior due to how kconfig
works. Which Boris patch is solving.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-06-17 20:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 10:37 [PATCH] ARM: fix DEBUG_UART_PHYS/VIRT issue when modifying DEBUG_LL output Boris Brezillon
2015-01-13 10:37 ` Boris Brezillon
2015-06-17 12:46 ` Thomas Petazzoni
2015-06-17 12:46   ` Thomas Petazzoni
2015-06-17 19:40   ` Russell King - ARM Linux
2015-06-17 19:40     ` Russell King - ARM Linux
2015-06-17 20:10     ` Thomas Petazzoni [this message]
2015-06-17 20:10       ` Thomas Petazzoni

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=20150617221004.58699b2e@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 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.