From: Rob Gubler <rgubler@gmail.com>
To: Wolfgang Denk <wd@denx.de>, Rob Gubler <rgubler@gmail.com>,
linuxppc-dev@ozlabs.org
Subject: Re: Ebony DTS compile error
Date: Tue, 27 Jan 2009 14:15:58 -0800 [thread overview]
Message-ID: <e4ef24880901271415q166a20e0m53d495c3dc2f80a3@mail.gmail.com> (raw)
In-Reply-To: <20090126232028.GB10495@yookeroo.seuss>
[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]
>
> > > Is anyone aware of a version of DTC that will compile the ebony.dts
> file
> > > included with the 2.6.24 kernel? Or, an updated ebony.dts file that
> works
> > > with DTC 1.2.0-gb2b4990b. Any other suggestions would be great.
> Thanks!
> >
> > Is there any specific reson for you to use the old 2.6.24 kernel?
> >
> > If not, I'd recommend that you clone the git repository and use recent
> > code - this will build fine with current versions of the dtc.
>
> I concur. If you really have to use the old kernel, you could
> manually update the dts to dts-v1 without making other changes, which
> should be relatively simple - that's just a matter of changing all
> numbers in the file from bare hex to C-style (decimal by default, 0x
> for hex, etc.) and adding the magic /dts-v1/ tag at the top.
My only attachment to this kernel is it looks like the IPIPE and Xenomai
patches have already been applied to the 2.6.24 kernel provided by ELDK
4.2. In the past applying these patches for an x86 machine wasn't always a
simple task. I was hoping to save myself some time.
What git URL / path do you recommend I use to clone the repository? I found
some instructions on rebuilding the ELDK from scratch (
http://www.denx.de/wiki/view/DULG/ELDKRebuilding). Are these the
instructions I should be following?
-Rob
[-- Attachment #2: Type: text/html, Size: 1769 bytes --]
next prev parent reply other threads:[~2009-01-27 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 1:07 Ebony DTS compile error Rob Gubler
2009-01-24 1:47 ` Wolfgang Denk
2009-01-26 23:20 ` David Gibson
2009-01-27 22:15 ` Rob Gubler [this message]
2009-01-27 23:26 ` Wolfgang Denk
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=e4ef24880901271415q166a20e0m53d495c3dc2f80a3@mail.gmail.com \
--to=rgubler@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=wd@denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).