mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ray Jui <ray.jui@broadcom.com>
To: "Florian Fainelli" <f.fainelli@gmail.com>,
	"Clément Péron" <peron.clem@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
	"Russell King" <linux@armlinux.org.uk>,
	linux-kernel@vger.kernel.org, "Tony Lindgren" <tony@atomide.com>,
	"Laura Abbott" <labbott@redhat.com>,
	"Scott Branden" <sbranden@broadcom.com>,
	"Jon Mason" <jonmason@broadcom.com>,
	"Ray Jui" <rjui@broadcom.com>,
	"BCM Kernel Feedback" <bcm-kernel-feedback-list@broadcom.com>,
	"Clément Peron" <clement.peron@devialet.com>
Subject: Re: [PATCH v2 1/2] ARM: debug: Add Iproc UART3 debug addresses
Date: Fri, 1 Jun 2018 10:54:32 -0700	[thread overview]
Message-ID: <152f524b-49c5-2fc3-8f65-b71f0241b530@broadcom.com> (raw)
In-Reply-To: <61a35071-4304-a25f-8c99-fe504b2c2346@gmail.com>

Sorry Florian, I had a couple issues with my email client yesterday and 
I'm not sure if you have received my reply.

Please see my reply inline.

On 5/31/2018 3:16 PM, Florian Fainelli wrote:
> 
> 
> On 05/31/2018 10:24 AM, Ray Jui wrote:
>>
>>
>> On 5/31/2018 1:22 AM, Clément Péron wrote:
>>> Hi Rai,
>>>
>>> On Wed, 30 May 2018 at 19:25, Ray Jui <ray.jui@broadcom.com> wrote:
>>>>
>>>> Hi Clément,
>>>>
>>>> Correct me if I'm wrong, but I thought the trend is to move to use
>>>> earlycon that can be activated from kernel command line for early print
>>>> before the serial driver is loaded.
>>>>
>>>> Have you tried earlcon?
>>> No, only tested this method.
>>>
>>> Thanks,
>>> Clement
>>>
>>
>> If I remember it correctly, I think the trend is to use earlycon. There
>> are obvious shortcomings by making this configuration compile time based.
> 
> This is true, though on ARM 32-bit kernels DEBUG_LL gets used by the
> kernel self-decompressor and also before earlycon has a chance to run,
> this is useful to debugging memory issues where your memory
> configuration is incorrect typically.
> 

This is true.

> Either way is fine with me (accepting or dropping) the patch, though
> there is probably minimal impact in just accepting such a change.
> 

Will leave the decision to you then.

Thanks,

Ray

  reply	other threads:[~2018-06-01 17:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30 13:19 Clément Péron
2018-05-30 13:19 ` [PATCH v2 2/2] ARM: debug: fix BCM2836 order entry Clément Péron
2018-06-04 21:12   ` Florian Fainelli
2018-05-30 17:25 ` [PATCH v2 1/2] ARM: debug: Add Iproc UART3 debug addresses Ray Jui
2018-05-31  8:22   ` Clément Péron
2018-05-31 17:24     ` Ray Jui
2018-05-31 22:16       ` Florian Fainelli
2018-06-01 17:54         ` Ray Jui [this message]
2018-06-04 21:12 ` Florian Fainelli

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=152f524b-49c5-2fc3-8f65-b71f0241b530@broadcom.com \
    --to=ray.jui@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=clement.peron@devialet.com \
    --cc=f.fainelli@gmail.com \
    --cc=jonmason@broadcom.com \
    --cc=labbott@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=peron.clem@gmail.com \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.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 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®