On Tue, 2015-04-21 at 08:25 -0500, Timur Tabi wrote:
Scott Wood wrote:
We want single-name config targets to still work from the user's
perspective, but we want to reduce the (often imperfect) duplication
under the hood.
Ok, then define a new Kconfig option that merge_config.sh will look
On Tue, 2015-04-21 at 13:11 -0500, Timur Tabi wrote:
On 04/21/2015 12:55 PM, Scott Wood wrote:
Ok, then define a new Kconfig option that merge_config.sh will look for.
So in p1_defconfig, there will be this line:
CONFIG_OTHER_DEFCONFIGS=fsl_basic_config
If you want to do that go
On 04/21/2015 12:55 PM, Scott Wood wrote:
Ok, then define a new Kconfig option that merge_config.sh will look for.
So in p1_defconfig, there will be this line:
CONFIG_OTHER_DEFCONFIGS=fsl_basic_config
If you want to do that go ahead. In the meantime we'll use the
mechanism that already
Scott Wood wrote:
We want single-name config targets to still work from the user's
perspective, but we want to reduce the (often imperfect) duplication
under the hood.
Ok, then define a new Kconfig option that merge_config.sh will look for.
So in p1_defconfig, there will be this line:
On Sat, 2015-04-18 at 08:46 -0500, Timur Tabi wrote:
On Fri, Apr 17, 2015 at 11:53 PM, Lijun Pan lijun@freescale.com wrote:
Have just sent out a patch considering the previous discussion.
http://patchwork.ozlabs.org/patch/462249/
[PATCH] powerpc/defconfig: new way of writing defconfig
On Mon, 2015-04-20 at 21:02 -0500, Timur Tabi wrote:
On Mon, Apr 20, 2015 at 3:31 PM, Scott Wood scottw...@freescale.com wrote:
The ability to merge configs is already there. We're just talking about
using that functionality.
Why do you need a powerpc-specific way to use
the subject of this thread, which is new way of writing
defconfigs for freescale's powerpc platforms.
Are you complaining about the actual content of which
fragments to use to produce which defconfigs going in arch/powerpc?
No, I'm just trying to figure out what's powerpc-specific about
On Mon, 2015-04-20 at 21:02 -0500, Timur Tabi wrote:
On Mon, Apr 20, 2015 at 3:31 PM, Scott Wood scottw...@freescale.com wrote:
The ability to merge configs is already there. We're just talking about
using that functionality.
Why do you need a powerpc-specific way to use
defconfigs for freescale's powerpc platforms.
Are you complaining about the actual content of which
fragments to use to produce which defconfigs going in arch/powerpc?
No, I'm just trying to figure out what's powerpc-specific about Lijun's
proposal.
Besides, wouldn't it make more sense to define
On Mon, Apr 20, 2015 at 3:31 PM, Scott Wood scottw...@freescale.com wrote:
The ability to merge configs is already there. We're just talking about
using that functionality.
Why do you need a powerpc-specific way to use merge_config.sh? Other
architectures have the same problem with
On Fri, Apr 17, 2015 at 11:53 PM, Lijun Pan lijun@freescale.com wrote:
Have just sent out a patch considering the previous discussion.
http://patchwork.ozlabs.org/patch/462249/
[PATCH] powerpc/defconfig: new way of writing defconfig
The ability to merge defconfigs is a feature that's been
-Original Message-
From: Bob Cochran [mailto:p...@mindchasers.com]
Sent: Thursday, April 16, 2015 8:21 AM
To: Wood Scott-B07421; Pan Lijun-B44306
Cc: linuxppc-...@ozlabs.org; Schmitt Richard-B43082
Subject: Re: new way of writing defconfigs for freescale's powerpc platforms
On Thu, 2015-04-16 at 23:13 -0500, Scott Wood wrote:
On Fri, 2015-04-17 at 10:54 +1000, Michael Ellerman wrote:
On Thu, 2015-04-09 at 21:52 +, Lijun Pan wrote:
Hi Maintainers,
We have a proposal for writing the defconfigs for freescale's powperpc
platforms in a new way.
Can
-Original Message-
From: Michael Ellerman [mailto:m...@ellerman.id.au]
Sent: Friday, April 17, 2015 1:19 AM
To: Wood Scott-B07421
Cc: Pan Lijun-B44306; linuxppc-...@ozlabs.org; Schmitt Richard-B43082
Subject: Re: new way of writing defconfigs for freescale's powerpc platforms
: new way of writing defconfigs for freescale's powerpc platforms
On Thu, 2015-04-16 at 23:13 -0500, Scott Wood wrote:
On Fri, 2015-04-17 at 10:54 +1000, Michael Ellerman wrote:
On Thu, 2015-04-09 at 21:52 +, Lijun Pan wrote:
Hi Maintainers,
We have a proposal for writing
-Original Message-
From: Wood Scott-B07421
Sent: Friday, April 17, 2015 1:53 PM
To: Pan Lijun-B44306
Cc: Michael Ellerman; linuxppc-...@ozlabs.org; Schmitt Richard-B43082
Subject: Re: new way of writing defconfigs for freescale's powerpc platforms
On Fri, 2015-04-17 at 13:50
-Original Message-
From: Wood Scott-B07421
Sent: Thursday, April 09, 2015 5:31 PM
To: Pan Lijun-B44306
Cc: linuxppc-...@ozlabs.org; Schmitt Richard-B43082
Subject: Re: new way of writing defconfigs for freescale's powerpc platforms
On Thu, 2015-04-09 at 16:52 -0500, Pan Lijun
On 04/16/2015 12:44 AM, Bob Cochran wrote:
On 04/09/2015 06:31 PM, Scott Wood wrote:
On Thu, 2015-04-09 at 16:52 -0500, Pan Lijun-B44306 wrote:
Hi Maintainers,
We have a proposal for writing the defconfigs for freescale's
powperpc platforms in a new way.
Can you take a look and provide some
On Thu, 2015-04-09 at 21:52 +, Lijun Pan wrote:
Hi Maintainers,
We have a proposal for writing the defconfigs for freescale's powperpc
platforms in a new way.
Can you take a look and provide some feedback?
You know currently we have mpc85xx_defconfig, corenet32_defconfig,
On Fri, 2015-04-17 at 10:54 +1000, Michael Ellerman wrote:
On Thu, 2015-04-09 at 21:52 +, Lijun Pan wrote:
Hi Maintainers,
We have a proposal for writing the defconfigs for freescale's powperpc
platforms in a new way.
Can you take a look and provide some feedback?
You know
On Thu, 2015-04-16 at 00:44 -0400, Bob Cochran wrote:
As you probably know, Freescale makes use of the Yocto Project build
system for its SDK and submits patches to the SDK at a public
meta-fsl-ppc repo at http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/
I have seen some kernel
On 04/09/2015 06:31 PM, Scott Wood wrote:
On Thu, 2015-04-09 at 16:52 -0500, Pan Lijun-B44306 wrote:
Hi Maintainers,
We have a proposal for writing the defconfigs for freescale's powperpc
platforms in a new way.
Can you take a look and provide some feedback?
You know currently we have
22 matches
Mail list logo