From: Bill Gatliff <bgat@billgatliff•com>
To: Matt Sealey <matt@genesi-usa•com>
Cc: 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 14:19:14 -0600 [thread overview]
Message-ID: <492C5DC2.9040402@billgatliff.com> (raw)
In-Reply-To: <b5e2fc790811251207g38d429f3q4eb698b92162d6@mail.gmail.com>
Matt Sealey wrote:
> 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?
That, and I prefer Free *ware whenever that's an option. :)
Nothing against the commercial alternatives, of course. But I'm
already doing my own heavy lifting, because my platforms are all
full-custom with very limited production runs. Since I'm into the
guts of all my code anyway, I'm not inclined to outsource a bootloader
development effort.
Just trying to figure out where the walls of this "sandbox" are. I've
been aware of the concept of Open Firmware for a while, but haven't
really looked into it before now--- mostly because my impression until
now was that the available implementations were both closed-source,
and not supporting embedded, non-PPC targets like ARM.
b.g.
--
Bill Gatliff
bgat@billgatliff•com
next prev parent reply other threads:[~2008-11-25 20:18 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
2008-11-25 20:46 ` Matt Sealey
2008-11-25 20:19 ` Bill Gatliff [this message]
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-25 21:14 ` Matt Sealey
2008-11-26 1:23 ` Mike Frysinger
2009-01-07 0:04 ` Benjamin Herrenschmidt
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=492C5DC2.9040402@billgatliff.com \
--to=bgat@billgatliff$(echo .)com \
--cc=gerickson@nuovations$(echo .)com \
--cc=linux-embedded@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=matt@genesi-usa$(echo .)com \
--cc=sr@denx$(echo .)de \
--cc=wd@denx$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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