linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* Migrating from ppc to powerpc
@ 2010-04-04  7:10 Shawn Jin
  2010-04-04  7:27 ` Grant Likely
  0 siblings, 1 reply; 3+ messages in thread
From: Shawn Jin @ 2010-04-04  7:10 UTC (permalink / raw)
  To: ppcdev

[-- Attachment #1: Type: text/plain, Size: 509 bytes --]

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?

Thanks alot,
-Shawn.

[-- Attachment #2: Type: text/html, Size: 550 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Migrating from ppc to powerpc
  2010-04-04  7:10 Migrating from ppc to powerpc Shawn Jin
@ 2010-04-04  7:27 ` Grant Likely
  2010-04-05  5:21   ` Shawn Jin
  0 siblings, 1 reply; 3+ messages in thread
From: Grant Likely @ 2010-04-04  7:27 UTC (permalink / raw)
  To: Shawn Jin; +Cc: ppcdev

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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Migrating from ppc to powerpc
  2010-04-04  7:27 ` Grant Likely
@ 2010-04-05  5:21   ` Shawn Jin
  0 siblings, 0 replies; 3+ messages in thread
From: Shawn Jin @ 2010-04-05  5:21 UTC (permalink / raw)
  To: Grant Likely; +Cc: ppcdev

[-- Attachment #1: Type: text/plain, Size: 671 bytes --]

On Sun, Apr 4, 2010 at 12:27 AM, Grant Likely <grant.likely@secretlab.ca>wrote:

> 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.
>

Thanks a lot for the info. The board has a MPC7448 processor. I certainly
like to post the .dts file for review and help.

-Shawn.

[-- Attachment #2: Type: text/html, Size: 1039 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-04-05  5:21 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-04  7:10 Migrating from ppc to powerpc Shawn Jin
2010-04-04  7:27 ` Grant Likely
2010-04-05  5:21   ` Shawn Jin

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).