From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Rafal Jaworowski <raj-nYOzD4b6Jr9Wk0Htik3J/w@public.gmane.org>
Cc: devicetree-discuss
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
Jeremy Kerr <jeremy.kerr-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Subject: Flattened Device Tree
Date: Thu, 21 Jan 2010 09:38:37 -0700 [thread overview]
Message-ID: <fa686aa41001210838k1fff33fbndf98e9d5a99dec2c@mail.gmail.com> (raw)
In-Reply-To: <fa686aa41001210833v7ac9c0a1gd5b40d0ff5bfdc32-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Oops, originally bcc'd the mailing list instead of cc'd. resend.
---------- Forwarded message ----------
Hey Rafal,
A friend pointed this status update out to me on the FreeBSD mailing
list. I'm thrilled to see that you're making progress.
I'm also working on adding Linux FDT support to the ARM architecture,
and I think we need to coordinate. Specifically, I'd like to agree on
a common boot interface for FDT booting on ARM (and PowerPC for that
matter).
For PowerPC, I assume you're adopting the boot interface specified in
ePAPR and are using r3 to pass the FDT blob pointer (page 53 of
ePAPR). Correct?
What are you using for the ARM boot interface? For the experiments
performed to date, the dtb is getting passed to the kernel in a new
ATAG, but I thing ATAGs are Linux specific. Ideally, I'd like to have
exactly one method of passing the dtb to the kernel, and I don't see
any good reason for Linux, FreeBSD, or any other OS to use different
methods. However, I also don't want to break booting older operating
system images that don't support FDT. The ATAG approach is nice for
Linux because it just adds an additional data item in a backwards
compatible way.
Thoughts?
g.
> ---------- Forwarded message ----------
> Flattened Device Tree for embedded FreeBSD
> URL: http://wiki.FreeBSD.org/FlattenedDeviceTree
> URL:
> http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/fdt/...
> Contact: Rafal Jaworowski <raj-nYOzD4b6Jr9Wk0Htik3J/w@public.gmane.org>
> The purpose of this project is to provide FreeBSD with support for the
> Flattened Device Tree (FDT) technology, the mechanism for describing
> computer hardware resources, which cannot be probed or self enumerated,
> in a uniform and portable way. The primary consumers of this technology
> are embedded FreeBSD platforms (ARM, AVR32, MIPS, PowerPC), where a lot
> of designs are based on similar chips but have different assignment of
> pins, memory layout, addresses bindings, interrupts routing and other
> resources.
> Current state highlights:
> * Environment, supported tools
> + Integrated device tree compiler (dtc) and libfdt into FreeBSD
> userspace, kernel and loader build
> * loader(8)
> + Full support for device tree blob handling
> + Load, traverse, modify (including add/remove) device tree
> nodes and properties
> + Pass the device tree blob to the kernel
> + Both ARM and PowerPC loader(8) supported
> * Kernel side FDT support (common)
> + Developed OF interface for FDT-backed platforms
> + ofw_bus I/F (and /dev/openfirm) available with FDT
> + Integrated FDT resources representation with newbus (fdtbus
> and simplebus drivers)
> * PowerPC kernel (Freescale MPC85XX SOC)
> + MPC8555CDS and MPC8572DS successfully converted to FDT
> conventions
> * ARM kernel (Marvell Orion, Kirkwood and Discovery SOC)
> + Work in progress on integrating FDT infrastructure with ARM
> platform code
> Work on this project has been sponsored by the FreeBSD Foundation.
> Open tasks:
> 1. Complete missing pieces for PowerPC (PCI bridge driver conversion
> to FDT).
> 2. Complete ARM support.
> 3. Merge to SVN.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next parent reply other threads:[~2010-01-21 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7f9d9abf1001180924o5b587b54i737d60467e3c878@mail.gmail.com>
[not found] ` <33307c791001191410r6430bb81wbfee8f9e82c5cbf9@mail.gmail.com>
[not found] ` <fa686aa41001210833v7ac9c0a1gd5b40d0ff5bfdc32@mail.gmail.com>
[not found] ` <fa686aa41001210833v7ac9c0a1gd5b40d0ff5bfdc32-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-21 16:38 ` Grant Likely [this message]
[not found] ` <fa686aa41001210838k1fff33fbndf98e9d5a99dec2c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-21 20:58 ` Flattened Device Tree Rafal Jaworowski
[not found] ` <85F0BAED-9E81-4C1D-ABA4-CE4EFF8198BD-nYOzD4b6Jr9Wk0Htik3J/w@public.gmane.org>
2010-01-21 21:22 ` Grant Likely
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=fa686aa41001210838k1fff33fbndf98e9d5a99dec2c@mail.gmail.com \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=jeremy.kerr-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=raj-nYOzD4b6Jr9Wk0Htik3J/w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox