From: "Jens Wirth" <jewirth@googlemail.com>
To: "Andrew Schmidt" <andrewgschmidt@gmail.com>,
linuxppc-embedded@ozlabs.org
Subject: Re: PPC to PowerPC Migration
Date: Thu, 12 Jun 2008 10:14:11 +0200 [thread overview]
Message-ID: <f944af2a0806120114o13a8f29u369ddb224d7d4495@mail.gmail.com> (raw)
In-Reply-To: <1A76658A-B5BB-4A48-B81A-A0F7096C2943@gmail.com>
On Wed, Jun 11, 2008 at 9:36 PM, Andrew Schmidt
<andrewgschmidt@gmail.com> wrote:
> First off, thank you everyone for replying, I must admit I was only
> expecting a few people to reply, but this is great. I certainly am
> interested in any help I can get. I suspect my first task is to go over the
> information given and then start to draft up a simple text file. I am more
> experienced with the Xilinx PPC so initially the documentation may seems a
> little biased, but if anyone with other areas of expertise (as is evident
> from the emails received thus far) wants to help broaden it, that would be
> great. I will get back to you shortly with my first "attempt."
I'm currently working with a custom design on a Xilinx ML300 board
to evaluate the realtime capabilities of the linux kernel with rt-patches.
Since this is my first experience with embedded Linux I had the most
trouble with understanding the coherences of the most general stuff
like the difference between ppc and powerpc as well as the need for
a device tree within powerpc but not ppc. Everything is documented
very well for it's own, but I would appreciate to see a documentation
that gives a bit more overview to the subject which is important for
beginners.
Well, I'm going to document my work from the system design using
EDK and ISE through to creating a running linux from scratch based
on this design. I'd like to support your documentation as much as I can.
Regards,
Jens Wirth
next prev parent reply other threads:[~2008-06-12 8:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 17:48 PPC to PowerPC Migration Andy Schmidt
2008-06-10 23:59 ` John Linn
2008-06-11 1:19 ` Mike Timmons
2008-06-11 13:55 ` vb
2008-06-11 14:03 ` Jon Loeliger
2008-06-11 15:33 ` vb
2008-06-11 15:45 ` Darcy Watkins
2008-06-11 16:03 ` vb
2008-06-11 16:07 ` Scott Wood
2008-06-11 14:38 ` Darcy Watkins
2008-06-11 16:32 ` Josh Boyer
2008-06-11 17:15 ` Darcy Watkins
2008-06-11 17:32 ` Josh Boyer
2008-06-11 17:52 ` Darcy Watkins
2008-06-11 17:56 ` Josh Boyer
2008-06-12 15:58 ` Darcy Watkins
2008-06-11 19:36 ` Andrew Schmidt
2008-06-12 8:14 ` Jens Wirth [this message]
2008-06-12 16:02 ` 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=f944af2a0806120114o13a8f29u369ddb224d7d4495@mail.gmail.com \
--to=jewirth@googlemail.com \
--cc=andrewgschmidt@gmail.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).