public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Valentine Barshak <vbarshak@ru•mvista.com>
To: Josh Boyer <jwboyer@linux•vnet.ibm.com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [PATCH 0/9] Rework PowerPC 44x board support
Date: Wed, 20 Aug 2008 20:51:18 +0400	[thread overview]
Message-ID: <48AC4B86.8010902@ru.mvista.com> (raw)
In-Reply-To: <cover.1219160188.git.jwboyer@linux.vnet.ibm.com>

Josh Boyer wrote:
> The following patch series reworks the board support code for PowerPC 44x
> platforms.  It eliminates a number of redundant <board>.c files and add a
> ppc44x_simple.c file that has an explicit list of boards that are supported
> by it.  This is the same mechanism that Grant Likely has used for MPC 5200
> boards.
> 
> It also adds some more explicit support for Glacier and Yosemite boards, as
> those boards were using a board level compatible property in their DTS files
> that was a bit confusing.
> 
> Review would be appreciated.  Tested on Sequoia, and I plan on testing on as
> many boards as I can before committing to my tree.
> 
> josh

Sorry if I miss anything, but
what happens if I build an uImage just for Rainier (not enabling other 
platforms in the kernel config) and then start it on Canyonlands for 
example?
They both use PowerPC_44x_simple stuff and looks like now we claim that 
all these "simple" boards are compatible. So, board check always passes, 
although Canyonlands support is actually disabled (CONFIG_460EX = n; 
CONFIG_PPC4xx_PCI_EXPRESS = n). It's not critical, but I just thought we 
might also remove the platform-specific options from 
arch/powerpc/platforms/44x/Kconfig for these boards at all. Just enable 
all board-specific stuff under "config PPC44x_SIMPLE".
Otherwise we probably should have a configurable char *board[] array.

Thanks,
Valentine.

  parent reply	other threads:[~2008-08-20 16:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 15:36 [PATCH 0/9] Rework PowerPC 44x board support Josh Boyer
2008-08-19 15:25 ` [PATCH 1/9] powerpc/44x: Add PowerPC 44x simple platform support Josh Boyer
2008-08-20 13:33   ` Arnd Bergmann
2008-08-20 14:03     ` Josh Boyer
2008-08-20 14:15     ` Grant Likely
2008-08-20 14:45       ` Josh Boyer
2008-08-20 15:19         ` Josh Boyer
2008-08-20 16:33         ` Roland Dreier
2008-08-20 17:11           ` Josh Boyer
2008-08-20 17:19             ` Roland Dreier
2008-08-20 17:35               ` Josh Boyer
2008-08-20 21:15                 ` Roland Dreier
2008-08-19 15:26 ` [PATCH 2/9] powerpc/44x: Migrate Bamboo support to ppc44x_simple Josh Boyer
2008-08-19 15:26 ` [PATCH 3/9] powerpc/44x: Migrate Canyonlands " Josh Boyer
2008-08-19 15:26 ` [PATCH 4/9] powerpc/44x: Migrate Katmai " Josh Boyer
2008-08-19 15:26 ` [PATCH 5/9] powerpc/44x: Migrate Rainier " Josh Boyer
2008-08-19 15:26 ` [PATCH 6/9] powerpc/44x: Migrate Sequoia " Josh Boyer
2008-08-19 15:26 ` [PATCH 7/9] powerpc/44x: Migrate Taishan " Josh Boyer
2008-08-19 15:27 ` [PATCH 8/9] powerpc/44x: Add explicit support for AMCC Glacier Josh Boyer
2008-08-19 15:27 ` [PATCH 9/9] powerpc/44x: Add explicit Yosemite support Josh Boyer
2008-08-19 18:26 ` [PATCH 0/9] Rework PowerPC 44x board support Stefan Roese
2008-08-19 18:45   ` Josh Boyer
2008-08-20 16:54     ` prodyut hazarika
2008-08-20 17:09       ` Josh Boyer
2008-08-20 16:51 ` Valentine Barshak [this message]
2008-08-20 17:08   ` Josh Boyer

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=48AC4B86.8010902@ru.mvista.com \
    --to=vbarshak@ru$(echo .)mvista.com \
    --cc=jwboyer@linux$(echo .)vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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