From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anatolij Gustschin <agust@denx.de>
Date: Thu, 15 Apr 2010 11:25:20 +0200
Subject: [U-Boot] [PATCH v3 3/3] mpc5121: pdm360ng: add coprocessor POST
In-Reply-To: <m2bpdlf50q.fsf@ohwell.denx.de>
References: <20100321192306.BFE104C022@gemini.denx.de>
	<1271254909-20398-1-git-send-email-agust@denx.de>
	<1271254909-20398-2-git-send-email-agust@denx.de>
	<1271254909-20398-3-git-send-email-agust@denx.de>
	<1271254909-20398-4-git-send-email-agust@denx.de>
	<20100414154016.C7A6DE85054@gemini.denx.de>
	<m2bpdlf50q.fsf@ohwell.denx.de>
Message-ID: <20100415112520.3b6c341d@wker>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Detlev,

On Thu, 15 Apr 2010 11:18:13 +0200
Detlev Zundel <dzu@denx.de> wrote:

...
> >> @@ -286,6 +287,18 @@ struct post_test post_list[] =
> >>  #if CONFIG_POST & CONFIG_SYS_POST_BSPEC5
> >>  	CONFIG_POST_BSPEC5,
> >>  #endif
> >> +#if CONFIG_POST & CONFIG_SYS_POST_COPROC
> >> +    {
> >> +	"Coprocessors communication test",
> >> +	"coproc_com",
> >> +	"This test checks communication with coprocessors.",
> >> +	POST_RAM | POST_ALWAYS | POST_CRITICAL,
> >> +	&pdm360ng_coprocessor_post_test,
> >> +	NULL,
> >> +	NULL,
> >> +	CONFIG_SYS_POST_COPROC
> >> +    }
> >> +#endif
> >>  };
> >
> > I don't want to see board specific code (pdm360ng_*) in such a global
> > file.  Please use a more generic approach.
> 
> Do you mean like for example CONFIG_POST_BSPEC1 used for lwmon5?
> 
> Anatolij, this should be straight forward.

Similar was in the first patch version. But according to Wolfgang
this doesn't belong in the board config file.

Anatolij