Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1167126 > unrolled thread

Re: [PATCH] ARM: fix DEBUG_UART_PHYS/VIRT issue when modifying DEBUG_LL output

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH] ARM: fix DEBUG_UART_PHYS/VIRT issue when modifying  DEBUG_LL output Russell King - ARM Linux <linux@arm.linux.org.uk> - 2015-06-17 21:50 +0200
    Re: [PATCH] ARM: fix DEBUG_UART_PHYS/VIRT issue when modifying  DEBUG_LL output Thomas Petazzoni <thomas.petazzoni@free-electrons.com> - 2015-06-17 22:20 +0200

#1167126 — Re: [PATCH] ARM: fix DEBUG_UART_PHYS/VIRT issue when modifying DEBUG_LL output

On Wed, Jun 17, 2015 at 02:46:56PM +0200, Thomas Petazzoni wrote:
> What is the status of this patch? It would actually be quite useful
> when switching back and forth between different DEBUG_LL configurations.
> 
> 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.

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1167134

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web