linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: Matt Sealey <matt@genesi-usa.com>
Cc: Bill Gatliff <bgat@billgatliff.com>,
	linux-embedded@vger.kernel.org, linuxppc-dev@ozlabs.org,
	Stefan Roese <sr@denx.de>, Wolfgang Denx <wd@denx.de>,
	Grant Erickson <gerickson@nuovations.com>
Subject: Re: [PATCH/RFC] Add Alternative Log Buffer Support for printk Messages
Date: Tue, 25 Nov 2008 13:17:26 -0700	[thread overview]
Message-ID: <fa686aa40811251217g6dcbef77u29e3d6ee6ad6d99f@mail.gmail.com> (raw)
In-Reply-To: <b5e2fc790811251207g38d429f3q4eb698b92162d6@mail.gmail.com>

On Tue, Nov 25, 2008 at 1:07 PM, Matt Sealey <matt@genesi-usa.com> wrote:
>
>
> On Tue, Nov 25, 2008 at 1:51 PM, Bill Gatliff <bgat@billgatliff.com> wrote:
>>
>> Matt Sealey wrote:
>>
>> > I can think of a bunch of reasons why it's a good idea..
>>
>> Can you point to a GPL/LGPL/BSD/etc. source code for an OpenFirmware
>> implementation?
>
> Yes, there's FirmWorks, CodeGen SmartFirmware, IBM SLOF and OpenBIOS..
> they're all linked from the OpenBIOS website (along with a bunch of the
> documentation from http://www.openfirmware.org in more-readable formats like
> PDF)
>
> http://www.openbios.org/
>
>
> But here's the real question; why do you need an opensource implementation?
> Curiosity?

Umm, so that it can be ported to new boards perhaps?  So that
developers can work with it?

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2008-11-25 20:17 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
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 [this message]
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=fa686aa40811251217g6dcbef77u29e3d6ee6ad6d99f@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=bgat@billgatliff.com \
    --cc=gerickson@nuovations.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).