From: Grant Likely <grant.likely@secretlab.ca>
To: Shawn Jin <shawnxjin@gmail.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>
Subject: Re: Migrating from ppc to powerpc
Date: Sun, 4 Apr 2010 01:27:27 -0600 [thread overview]
Message-ID: <y2ufa686aa41004040027p560c1b8bw6cdf3f096398cd42@mail.gmail.com> (raw)
In-Reply-To: <h2nc3d0340b1004040010ga00f75b6k38eccbe66ce11799@mail.gmail.com>
On Sun, Apr 4, 2010 at 1:10 AM, Shawn Jin <shawnxjin@gmail.com> wrote:
> Hi,
>
> I have a project that needs port ppc drivers to the powerpc arch. I've been
> searching the mailing list for some clues on what tasks they would look like
> and where should be the starting point. It's been quite a while since the
> powerpc arch started so the info is huge. The searching doesn't seem to be
> easy task for itself. :(
>
> Would gurus here shed some light? One thing I know of is a device tree.
> Assuming a device tree is provided, how much work would it be for driver
> porting?
What processor/board/soc are you using? The easiest path is to start
with a similar board and adapt the device tree source file (.dts in
arch/powerpc/boot/dts) to match your board with your devices. You'll
need to add a node to the tree for each device you add. If you post
your new .dts file to devicetree-discuss@lists.ozlabs.org for review,
then I and others will help you to craft it and get it into the format
that it needs to be in.
Porting device drivers is relatively straight forward. At the moment
you need to change your platform_drivers into of_platform_drivers.
Search the drivers/ tree for of_platform_driver to see lots of
examples of what these should look like.
Cheers,
g.
next prev parent reply other threads:[~2010-04-04 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 7:10 Migrating from ppc to powerpc Shawn Jin
2010-04-04 7:27 ` Grant Likely [this message]
2010-04-05 5:21 ` Shawn Jin
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=y2ufa686aa41004040027p560c1b8bw6cdf3f096398cd42@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=shawnxjin@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).