All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Mitidieri <cam@sysgo.com>
To: Florian Fainelli <florian@openwrt.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Boot program interface
Date: Mon, 20 Apr 2009 12:14:40 +0200	[thread overview]
Message-ID: <1240222480.49ec4b105b59b@www.sysgo.com> (raw)
In-Reply-To: <200904201057.04833.florian@openwrt.org>

Hi,

> Hi Carlos,
>
> Le Monday 20 April 2009 09:37:25 Carlos Mitidieri, vous avez écrit :
> > Hello,
> >
> > I am working on a project that requires an extensive boot program
> > interface.
> >
> > It turns out that the device tree used on PPC architecture meets the
> > requirements.
> >
> > I have been looking, and I could not find any similar concept implemented
> > for MIPS.
>
> I do not know any MIPS board using a device tree either.
>
> >
> > So, I am now considering to port the OFDT library into the MIPS arch.
> >
> > What do you think about this? Is there anyone working on a similar project?
>
> You should see how Sparc, PowerPC and Microblaze use it and how they do share
> code. Also condiser seeing how u-boot handles device trees, specifically on
> PowerPC and Microblaze.


Ok, but what you think about doing such a port? I mean, is it something that
could be eventually accepted by the MIPS Linux community? Or do you have
problems with this approach?

I am looking forward for your answers.

Kind regards,

-- 
Carlos Mitidieri
Project Engineer

  reply	other threads:[~2009-04-20 10:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20  7:37 Boot program interface Carlos Mitidieri
2009-04-20  8:57 ` Florian Fainelli
2009-04-20 10:14   ` Carlos Mitidieri [this message]
2009-04-20 20:07   ` David VomLehn (dvomlehn)
2009-04-20 20:07     ` David VomLehn (dvomlehn)
2009-04-21  6:32     ` Carlos Mitidieri

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=1240222480.49ec4b105b59b@www.sysgo.com \
    --to=cam@sysgo.com \
    --cc=florian@openwrt.org \
    --cc=linux-mips@linux-mips.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.