From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@linux-mips.org
Cc: Grant Likely <grant.likely@secretlab.ca>,
Imre Kaloz <kaloz@openwrt.org>, Gabor Juhos <juhosg@openwrt.org>,
John Crispin <blogic@openwrt.org>,
Dezhong Diao <dediao@cisco.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Converting MIPS to Device Tree
Date: Mon, 6 Jun 2011 02:07:53 +0100 [thread overview]
Message-ID: <20110606010753.GA16202@linux-mips.org> (raw)
Over the past few days I've started to convert arch/mips to use DT. So
far none of the platforms (except maybe PowerTV?) seems to have a
firmware that is passing a DT nor is there any 2nd stage bootloader that
could do so.
So as the 2nd best thing I've been working on .dts files to be compiled
into the images.
I've put a git tree of my current working tree online. It's absolutely
work in progress so expect to encounter bugs.
http://git.linux-mips.org/?p=linux-dt.git;a=summary (Gitweb)
git://git.linux-mips.org/linux-dt.git
http://www.linux-mips.org/wiki/Device_Tree (brief documentation & links)
An incomplete to do list:
o Sort out interface for firmware to pass a DT to the kernel. Because we
have so many different firmware implementations this one might get a
slight bit interesting.
o Interface to select one of several builtin DT images. I am thinking of
extending the existing MIPS_MACHINE() / machtype mechanism to play
nicely with DT.
o Finish and test AR7, Cobalt, Jazz, Malta, MIPSsim and SNI ports.
o Convert the remaining platforms; find if it's actually sensible to
convert all platforms.
o I'm considering to make DT support a requirement for future MIPS
platforms so you might as well start beating your firmware monkeys /
ask Santa to put you a shiny new bootloader blob into the boot now.
o Write more of the required infrastructure.
o Write documentation
Contributions and comments welcome,
Ralf
next reply other threads:[~2011-06-06 1:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 1:07 Ralf Baechle [this message]
2011-06-06 4:41 ` Converting MIPS to Device Tree Grant Likely
2011-06-07 23:02 ` David VomLehn
2011-06-07 23:22 ` David Daney
2011-06-08 1:09 ` David VomLehn
2011-06-10 18:57 ` Ralf Baechle
2011-06-10 19:00 ` David Daney
2011-06-08 7:15 ` Geert Uytterhoeven
2011-06-08 10:10 ` Florian Fainelli
2011-06-12 18:20 ` Florian Fainelli
2011-06-13 5:10 ` Grant Likely
2011-06-09 2:19 ` Tonyliu
2011-06-09 2:19 ` Tonyliu
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=20110606010753.GA16202@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=blogic@openwrt.org \
--cc=dediao@cisco.com \
--cc=grant.likely@secretlab.ca \
--cc=juhosg@openwrt.org \
--cc=kaloz@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=tglx@linutronix.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 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.