linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Becky Bruce <becky.bruce@freescale.com>
To: linuxppc64-dev@ozlabs.org, linuxppc-dev@ozlabs.org
Subject: RFC: proposed arch/powerpc directory structure
Date: Wed, 10 Aug 2005 11:45:10 -0500	[thread overview]
Message-ID: <c237b7e878e0c32f421209fa37b7a156@freescale.com> (raw)

All,

In the name of moving the much-anticipated 32/64 ppc merge along, Kumar 
Gala, Jon Loeliger, and myself have worked out an initial proposal for 
the directory structure of the new merged arch/powerpc.  Listed below 
are the proposed directories, along with a description of the logical 
contents, as well as a description of which existing files will be 
moved into these directories.

There was some discussion on the list recently about whether or not it 
might be better to change things around to be laid out more along the 
lines of functionality with, say, all pci-related code in one place.  
We've stuck with a more traditional model in this proposal, although 
the topic is certainly still up for discussion.

This is just a first pass at a structure - we're really looking for 
input from this list on the best way to proceed, and that discussion 
needs to start somewhere.  BTW, this proposal preempts the previous 
64-bit directory structure reorg proposal that I sent to this list a 
couple of months ago.

So here it is:

include/powerpc/

arch/powerpc/
	configs/
		- Kconfig defaults per buildable board.

	boot/
		- Pre-kernel execution shims and pre-passes.
		- Convert firmware reprensentations (bi_recs, OF Dev-Trees,
		 bootx,bd_t) to flat-dev-trees.
		- Includes merged files from arch/ppc*/boot/ trees, plus
		prom_init.c from arch/ppc64/kernel.

	kernel/
		- CPU-centric core code and generic PPC-specific kernel
		- Main entry point supports r5=0, r3 = flat-dev-tree, etc.
		- Includes all cpu core-specific code, kernel initialization code,
		and other generic kernel foo like smp, ptrace, syscalls, etc from
		arch/ppc*/kernel.  Files not belonging to one of these categories
		will be moved to other directories.


	platforms/
		- platform-specific code laid out in the following directories:
		pSeries/
		iSeries/
		pmac/  (both 32 and 64-bit)
		classic32/  (platforms containing 6xx/7xx/74xx/8240/8241/8245)
		classic64/  (Maple?)
		83xx/ (may collapse into classic 32 at some point)
		86xx/ (may collapse into classic 32 at some point)
		pq2/ (may collapse into classic 32 at some point)
		52xx/ (may collapse into classic 32 at some point)
		85xx/
		4xx/
		8xx/
		- Includes all code from arch/ppc/platforms, all code from
		arch/ppc64/kernel that is specific to a given platform (where a
		platform is a whole computer system or board)
	
		NOTE: there would be no .[chS] files directly under platforms -
		all live in subdirs.

	mm/
		- Memory management, slabs, tlbs, etc.
		- Unify LMB and mem_pieces for early boot memory.
		- Includes all code from arch/ppc*/mm

	sysdev/
		- System Device support and Kitchen Sink
		- Includes all code currently in arch/ppc/syslib, irq and pci code
		that currently lives in arch/ppc/kernel, and all code from
		arch/ppc64/kernel that is generic system code, including pci,
		irq, interrupt control, bridges, rtas(?)

	lib/
		- Library code
		- Includes all code from arch/ppc*/lib

	math-emu/
		- Math Emulation for FPU-less ppc32s.
		- this is 32-bit only, so this directory would just move from
		arch/ppc to arch/powerpc

	oprofile/
		- Support for oprofile.
		- Includes all code from arch/ppc*/oprofile

	xmon/
		- Support for xmon.
		- Includes all code from arch/ppc*xmon


Cheers,
-Becky

             reply	other threads:[~2005-08-10 16:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-10 16:45 Becky Bruce [this message]
2005-08-10 17:01 ` RFC: proposed arch/powerpc directory structure Dan Malek
2005-08-10 21:35   ` John W. Linville
2005-08-11  0:09 ` Stephen Rothwell
2005-08-11  1:10   ` Olof Johansson
2005-08-11 19:59 ` Tom Rini
2005-08-11 20:13   ` Kumar Gala
2005-08-11 20:18     ` Tom Rini
2005-08-11 22:41       ` Becky Bruce
2005-08-11 23:07       ` Kumar Gala
2005-08-11 23:19         ` Tom Rini
2005-08-12  2:34           ` Kumar Gala
2005-08-12  3:38             ` Tom Rini
2005-08-11 23:29         ` Dan Malek
2005-08-12  2:09   ` Josh Boyer
2005-08-12  3:49   ` Paul Mackerras
2005-08-12  4:14     ` Tom Rini
2005-08-15 18:25       ` Segher Boessenkool
2005-08-11 20:25 ` Olaf Hering

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=c237b7e878e0c32f421209fa37b7a156@freescale.com \
    --to=becky.bruce@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc64-dev@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).