From: Kumar Gala <kumar.gala@freescale.com>
To: "Povolotsky, Alexander" <Alexander.Povolotsky@marconi.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: seeking advise on porting custom PPC platform (in my case it is variant of 8xx ) from Linux 2.4.(.26) to Linux 2.6(.10-rc3)
Date: Sat, 25 Dec 2004 10:18:37 -0600 [thread overview]
Message-ID: <A1E3B6C2-5690-11D9-A059-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <313680C9A886D511A06000204840E1CF0A647403@whq-msgusr-02.pit.comms.marconi.com>
Alex,
Its my understanding that code moved out of arch/ppc/platforms and=20
arch/ppc/kernel in 2.4 into arch/ppc/syslib. The code in 'syslib'=20
deals with items that are not directly related with the CPU cores=20
(arch/ppc/kernel) or with board issues (arch/ppc/platforms). Any code=20=
that is generic for a number of systems should be in arch/ppc/syslib. =20=
So code managing pci, interrupt controllers, generic system setup, etc=20=
lives in arch/ppc/syslib.
The transition predates my work with 2.6, I would guess that Paul M.=20
was influential in this change.
If you are just doing a board port then your files should end up in=20
arch/ppc/platforms. It should be rare that you would need to touch=20
anything in arch/ppc/syslib.
- kumar
On Dec 24, 2004, at 11:05 AM, Povolotsky, Alexander wrote:
> Hi,
>
> In Linux 2.6 I see the new directory arch/ppc/syslib, which does not=20=
> exist
> in Linux 2.4(.26).
> I would GREATLY APPRECIATE if Tom or Dan (or someone else) could=20
> explain
> what are the reasons for creating this new directory and describe on=20=
> what
> basis existing
> Linux 2.4 files went there and why=A0 ...
> and if there any new files (vs Linux 2.4) were created in that new=20
> directory
> ?=A0
>
> In general, I am seeking advise on porting PPC platform
> (in my case it isvariant of 8xx ) from Linux 2.4.(.26) to Linux
> 2.6(.10-rc3).
> =A0Did anyone created howto document on this subject ?
>
> Thanks,
>
> Alex
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
prev parent reply other threads:[~2004-12-25 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-24 17:05 seeking advise on porting custom PPC platform (in my case it is variant of 8xx ) from Linux 2.4.(.26) to Linux 2.6(.10-rc3) Povolotsky, Alexander
2004-12-25 16:18 ` Kumar Gala [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=A1E3B6C2-5690-11D9-A059-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=Alexander.Povolotsky@marconi.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