linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Erickson <gerickson@nuovations.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>,
	Matt Sealey <matt@genesi-usa.com>
Cc: linuxppc-dev@ozlabs.org, Stefan Roese <sr@denx.de>,
	Wolfgang Denx <wd@denx.de>,
	linux-embedded@vger.kernel.org
Subject: Re: [PATCH/RFC] Add Alternative Log Buffer Support for printk Messages
Date: Tue, 25 Nov 2008 11:04:15 -0800	[thread overview]
Message-ID: <C5518C2F.13137%gerickson@nuovations.com> (raw)
In-Reply-To: <20081125135519.038abf23@zod.rchland.ibm.com>

On 11/25/08 10:55 AM, Josh Boyer wrote:
> On Tue, 25 Nov 2008 12:53:12 -0600
> "Matt Sealey" <matt@genesi-usa.com> wrote:
>> Nitpick, really.. shouldn't the logbuffer location(s) be some device tree
>> property(ies), perhaps something in the
>> /chosen node that U-Boot etc. can then fill out?
> 
> I don't think that's a nitpick.  It's a fundamental change in how this
> would all work.  However, I do think you're generally right.
> 
> Perhaps not /chosen, but maybe something like /rtas or /firmware, etc.

I'm inclined to agree with you both; however, the submitted implementation
was a choice of expediency given the existing DENX implementation and a
customer that needed the feature "yesterday".

ARM, MIPS, et al have not yet adopted device trees, correct? If so, is there
value in providing the submitted implementation and adding support for
getting said information from the device tree as another option if such
information exists?

Regards,

Grant


  parent reply	other threads:[~2008-11-25 19:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25 18:34 [PATCH/RFC] Add Alternative Log Buffer Support for printk Messages Grant Erickson
2008-11-25 18:53 ` Matt Sealey
2008-11-25 18:55   ` Josh Boyer
2008-11-25 19:01     ` Matt Sealey
2008-11-25 19:04     ` Grant Erickson [this message]
2008-11-25 19:31       ` Matt Sealey
2008-11-25 19:51         ` Bill Gatliff
2008-11-25 20:07           ` Matt Sealey
2008-11-25 20:17             ` Grant Likely
2008-11-25 20:46               ` Matt Sealey
2008-11-25 20:19             ` Bill Gatliff
2008-11-25 20:54               ` David VomLehn
2008-11-25 21:45                 ` David Brownell
2008-11-26 20:57                   ` Matt Sealey
2008-11-25 20:14           ` Grant Likely
2008-11-25 21:05         ` Wolfgang Denk
2008-11-26  1:23 ` Mike Frysinger
2009-01-07  0:04 ` Benjamin Herrenschmidt
2009-01-07  2:11   ` Grant Erickson
2009-01-07  2:11   ` Grant Erickson

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=C5518C2F.13137%gerickson@nuovations.com \
    --to=gerickson@nuovations.com \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=matt@genesi-usa.com \
    --cc=sr@denx.de \
    --cc=wd@denx.de \
    /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).