From: "M. Warner Losh" <imp@bsdimp•com>
To: linuxppc-embedded@ozlabs•org
Subject: Quick question about dts
Date: Tue, 05 Aug 2008 00:56:49 -0600 (MDT) [thread overview]
Message-ID: <20080805.005649.1713918190.imp@bsdimp.com> (raw)
I have a .dts file that works with 2.6.18 (MV Pro 5.0). I encode it
directly into the kernel image. However, when I try to use it with my
2.6.23, 2.6.24 or 2.6.25 kernel trees, it doesn't work at all. In the
MV Pro 5.0 kernel, I hacked the startup sequence to store a pointer to
this blob in r3 so that it is moved in. I've done something similar
in -current (for reasons that are too complicated to really explain
well, we can't do this via the normal boot loader mechanisms). The
dtc complains that the interrupt-controller property is obsolete on
the chosen device.
Does any documentation exist for how dts has evolved? I'd like to
forward port what I have without examining the .dts files from both
versions and guessing...
Warner
next reply other threads:[~2008-08-05 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 6:56 M. Warner Losh [this message]
2008-08-05 7:35 ` Quick question about dts Marco Stornelli
2008-08-05 14:41 ` Warner Losh
2008-08-06 12:22 ` Matt Sealey
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=20080805.005649.1713918190.imp@bsdimp.com \
--to=imp@bsdimp$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/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