linux-mips
[Top] [All Lists]

Re: Boot program interface

To: Florian Fainelli <florian@openwrt.org>
Subject: Re: Boot program interface
From: Carlos Mitidieri <cam@sysgo.com>
Date: Mon, 20 Apr 2009 12:14:40 +0200
Cc: linux-mips@linux-mips.org
In-reply-to: <200904201057.04833.florian@openwrt.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <1240213045.49ec26350fa49@www.sysgo.com> <200904201057.04833.florian@openwrt.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Internet Messaging Program (IMP) 3.2.6
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

<Prev in Thread] Current Thread [Next in Thread>