From: Wolfgang Denk <wd@denx.de>
To: Rob Gubler <rgubler@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Ebony DTS compile error
Date: Wed, 28 Jan 2009 00:26:48 +0100 [thread overview]
Message-ID: <20090127232648.8B49C832E416@gemini.denx.de> (raw)
In-Reply-To: <e4ef24880901271415q166a20e0m53d495c3dc2f80a3@mail.gmail.com>
Dear Rob Gubler,
In message <e4ef24880901271415q166a20e0m53d495c3dc2f80a3@mail.gmail.com> you wrote:
>
> 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.
You will find that applying the Xenomai patches to our tree is really
straightforward. The last version that has received "official" support
(i. e was added to Xenomai mainline) is v2.6.28, and tested with our tree.
> What git URL / path do you recommend I use to clone the repository? I found
http://git.denx.de/?p=linux-2.6-denx.git
> some instructions on rebuilding the ELDK from scratch (
> http://www.denx.de/wiki/view/DULG/ELDKRebuilding). Are these the
> instructions I should be following?
Please see http://www.denx.de/wiki/view/DULG/LinuxConfiguration
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
I have often regretted my speech, never my silence.
prev parent reply other threads:[~2009-01-27 23:26 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
2009-01-27 23:26 ` Wolfgang Denk [this message]
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=20090127232648.8B49C832E416@gemini.denx.de \
--to=wd@denx.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=rgubler@gmail.com \
/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).