linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@freescale.com>
To: vb <vb@vsbe.com>
Cc: Mike Timmons <mike_timmons@trimble.com>,
	Andy Schmidt <andrewgschmidt@gmail.com>,
	linuxppc-embedded@ozlabs.org
Subject: Re: PPC to PowerPC Migration
Date: Wed, 11 Jun 2008 09:03:41 -0500	[thread overview]
Message-ID: <484FDB3D.4040101@freescale.com> (raw)
In-Reply-To: <f608b67d0806110655v19dac162wc3adfc8939b5c40a@mail.gmail.com>

vb wrote:
> I recently ported two platforms (8245 and 8541) from ppc tree in
> earlier 2.6 versions into powerpc tree in 2.6.25. It is amazing how
> little the device tree contents are described, a lot of things
> required reverse engineering of the kernel code to understand the
> meaning of some numbers in the  tree.
> 
> I am also willing to contribute into a document describing this
> transition, please keep me in the loop,
> 
> regards,
> Vadim


Well, perhaps as a starting point you could tell us
which things required reverse engineering or what you
were not able to find in a document?

Thanks,
jdl

  reply	other threads:[~2008-06-11 14:03 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 [this message]
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
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=484FDB3D.4040101@freescale.com \
    --to=jdl@freescale.com \
    --cc=andrewgschmidt@gmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=mike_timmons@trimble.com \
    --cc=vb@vsbe.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).