linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-dev@ozlabs.org,
	Gill Becky-BGILL <becky.bruce@freescale.com>,
	linuxppc64-dev@ozlabs.org
Subject: Re: RFC: proposed arch/powerpc directory structure
Date: Thu, 11 Aug 2005 16:19:48 -0700	[thread overview]
Message-ID: <20050811231948.GA3187@smtp.west.cox.net> (raw)
In-Reply-To: <DE2CC80C-91A2-4860-B452-6AD171F3588A@freescale.com>

On Thu, Aug 11, 2005 at 06:07:03PM -0500, Kumar Gala wrote:
[snip]
> I think this causes confusion.  the reason we suggested pq2 and  
> classic32 was to handle things like sandpoint.  Sandpoint would live  
> in classic32.  The confusion partial comes from the fact that we can  
> run 8240/1/5 on a Sandpoint.  The thinking was everything that was  
> 6xx/7xx/74xx + things like 8240/1/5 which can be thought of as 603 +  
> 10x bridge would be classic32.

Thanks for the explanation.  But I think this is overkill for the
sandpoint or true like a sandpoint (Zynx something, Willow, neither of
which are in the kernel tree).  I think we can field the "I wanna hack
on my Sandpoint/8240, but don't see the code under 82xx/!" question. :)

> If it was 82xx w/o a CPM it went into classic32.  If it was a 82xx w/ 
> CPM it went into pq2.  The idea being that we might be able to build  
> kernels in either directory that supported a large number of boards  
> with one image.

We can certainly investigate just how many distinct boards can be
supported with one image when infos are passed dynamically.  If we can
simplify things enough, maybe we can break the rule of no .[ch] files in
arch/powerpc/platforms since it'll just be 82xx.[ch], 83xx.[ch] and so
on, execept for that damn pmac. ;)

-- 
Tom Rini
http://gate.crashing.org/~trini/

  reply	other threads:[~2005-08-11 23:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-10 16:45 RFC: proposed arch/powerpc directory structure Becky Bruce
2005-08-10 17:01 ` 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 [this message]
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=20050811231948.GA3187@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=becky.bruce@freescale.com \
    --cc=kumar.gala@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).