Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Friday 19 February 2016 18:07:25 Russell King - ARM Linux wrote: > On Fri, Feb 19, 2016 at 12:31:02PM -0500, Nicolas Pitre wrote: > > Yet, the only reason for a default here is to accommodate automatic > > build tests like randconfig, right? > > > > If so then this should be "fixed" by having

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Friday 19 February 2016 18:07:25 Russell King - ARM Linux wrote: > On Fri, Feb 19, 2016 at 12:31:02PM -0500, Nicolas Pitre wrote: > > Yet, the only reason for a default here is to accommodate automatic > > build tests like randconfig, right? > > > > If so then this should be "fixed" by having

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Fri, Feb 19, 2016 at 12:31:02PM -0500, Nicolas Pitre wrote: > Yet, the only reason for a default here is to accommodate automatic > build tests like randconfig, right? > > If so then this should be "fixed" by having the config system provide > built-in symbols that can be tested from kconfig

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Fri, Feb 19, 2016 at 12:31:02PM -0500, Nicolas Pitre wrote: > Yet, the only reason for a default here is to accommodate automatic > build tests like randconfig, right? > > If so then this should be "fixed" by having the config system provide > built-in symbols that can be tested from kconfig

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Fri, 19 Feb 2016, Russell King - ARM Linux wrote: > ARM_PATCH_PHYS_VIRT exists to support an init-time decided phys offset, > and it supports this by modifying each location that the phys offset > is used. It determines this by looking at the location that the early > init code is executing,

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Fri, 19 Feb 2016, Russell King - ARM Linux wrote: > ARM_PATCH_PHYS_VIRT exists to support an init-time decided phys offset, > and it supports this by modifying each location that the phys offset > is used. It determines this by looking at the location that the early > init code is executing,

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Fri, 19 Feb 2016, Arnd Bergmann wrote: > On Friday 19 February 2016 11:10:22 Nicolas Pitre wrote: > > On Fri, 19 Feb 2016, Arnd Bergmann wrote: > > > > > On Thursday 18 February 2016 11:02:33 Nicolas Pitre wrote: > > > > > > > > Acked-by: Nicolas Pitre > > > > > > > > Is

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Fri, 19 Feb 2016, Arnd Bergmann wrote: > On Friday 19 February 2016 11:10:22 Nicolas Pitre wrote: > > On Fri, 19 Feb 2016, Arnd Bergmann wrote: > > > > > On Thursday 18 February 2016 11:02:33 Nicolas Pitre wrote: > > > > > > > > Acked-by: Nicolas Pitre > > > > > > > > Is there a way to

RE: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On 19 Feb 2016, Russell King wrote: > Using the DTB location on XIP platforms is a no-goer - the flattened > DTB information can be fixed, so on an XIP platform it makes sense > for this to also be in flash, not in RAM (the whole point of XIP is > to remove constant data from RAM after all, so

RE: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On 19 Feb 2016, Russell King wrote: > Using the DTB location on XIP platforms is a no-goer - the flattened > DTB information can be fixed, so on an XIP platform it makes sense > for this to also be in flash, not in RAM (the whole point of XIP is > to remove constant data from RAM after all, so

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Fri, Feb 19, 2016 at 04:34:51PM +0100, Arnd Bergmann wrote: > On Friday 19 February 2016 14:29:00 Chris Brandt wrote: > > On 19 Feb 2016, Arnd Bergmann wrote: > > > > > On Thursday 18 February 2016 11:02:33 Nicolas Pitre wrote: > > > > > > > > Acked-by: Nicolas Pitre > > > >

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Fri, Feb 19, 2016 at 04:34:51PM +0100, Arnd Bergmann wrote: > On Friday 19 February 2016 14:29:00 Chris Brandt wrote: > > On 19 Feb 2016, Arnd Bergmann wrote: > > > > > On Thursday 18 February 2016 11:02:33 Nicolas Pitre wrote: > > > > > > > > Acked-by: Nicolas Pitre > > > > > > > > Is

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Friday 19 February 2016 11:10:22 Nicolas Pitre wrote: > On Fri, 19 Feb 2016, Arnd Bergmann wrote: > > > On Thursday 18 February 2016 11:02:33 Nicolas Pitre wrote: > > > > > > Acked-by: Nicolas Pitre > > > > > > Is there a way to provide a default for defaults? ... > > and

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Friday 19 February 2016 11:10:22 Nicolas Pitre wrote: > On Fri, 19 Feb 2016, Arnd Bergmann wrote: > > > On Thursday 18 February 2016 11:02:33 Nicolas Pitre wrote: > > > > > > Acked-by: Nicolas Pitre > > > > > > Is there a way to provide a default for defaults? ... > > and then select one of

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Fri, 19 Feb 2016, Arnd Bergmann wrote: > On Thursday 18 February 2016 11:02:33 Nicolas Pitre wrote: > > > > Acked-by: Nicolas Pitre > > > > Is there a way to provide a default for defaults? > > We could have something like > > config PHYS_OFFSET_0 > bool > > config

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Fri, 19 Feb 2016, Arnd Bergmann wrote: > On Thursday 18 February 2016 11:02:33 Nicolas Pitre wrote: > > > > Acked-by: Nicolas Pitre > > > > Is there a way to provide a default for defaults? > > We could have something like > > config PHYS_OFFSET_0 > bool > > config PHYS_OFFSET_1 >

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Friday 19 February 2016 14:29:00 Chris Brandt wrote: > On 19 Feb 2016, Arnd Bergmann wrote: > > > On Thursday 18 February 2016 11:02:33 Nicolas Pitre wrote: > > > > > > Acked-by: Nicolas Pitre > > > > > > Is there a way to provide a default for defaults? > > > > We could

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Friday 19 February 2016 14:29:00 Chris Brandt wrote: > On 19 Feb 2016, Arnd Bergmann wrote: > > > On Thursday 18 February 2016 11:02:33 Nicolas Pitre wrote: > > > > > > Acked-by: Nicolas Pitre > > > > > > Is there a way to provide a default for defaults? > > > > We could have something

RE: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On 19 Feb 2016, Arnd Bergmann wrote: > On Thursday 18 February 2016 11:02:33 Nicolas Pitre wrote: > > > > Acked-by: Nicolas Pitre > > > > Is there a way to provide a default for defaults? > > We could have something like > > config PHYS_OFFSET_0 > bool > > config

RE: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On 19 Feb 2016, Arnd Bergmann wrote: > On Thursday 18 February 2016 11:02:33 Nicolas Pitre wrote: > > > > Acked-by: Nicolas Pitre > > > > Is there a way to provide a default for defaults? > > We could have something like > > config PHYS_OFFSET_0 > bool > > config PHYS_OFFSET_1 >

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Thursday 18 February 2016 11:02:33 Nicolas Pitre wrote: > > Acked-by: Nicolas Pitre > > Is there a way to provide a default for defaults? We could have something like config PHYS_OFFSET_0 bool config PHYS_OFFSET_1 bool config PHYS_OFFSET_2 bool

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Thursday 18 February 2016 11:02:33 Nicolas Pitre wrote: > > Acked-by: Nicolas Pitre > > Is there a way to provide a default for defaults? We could have something like config PHYS_OFFSET_0 bool config PHYS_OFFSET_1 bool config PHYS_OFFSET_2 bool ... (we need 8 of

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Thu, 18 Feb 2016, Arnd Bergmann wrote: > For platforms that are not yet converted to ARCH_MULTIPLATFORM, > we can disable CONFIG_ARM_PATCH_PHYS_VIRT, which in turn requires > setting a correct address here. > > As we actualy know what all the values are supposed to be based > on the old

Re: [PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

On Thu, 18 Feb 2016, Arnd Bergmann wrote: > For platforms that are not yet converted to ARCH_MULTIPLATFORM, > we can disable CONFIG_ARM_PATCH_PHYS_VIRT, which in turn requires > setting a correct address here. > > As we actualy know what all the values are supposed to be based > on the old

[PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

For platforms that are not yet converted to ARCH_MULTIPLATFORM, we can disable CONFIG_ARM_PATCH_PHYS_VIRT, which in turn requires setting a correct address here. As we actualy know what all the values are supposed to be based on the old mach/memory.h header file contents (from git history), we

[PATCH 4/9] ARM: add CONFIG_PHYS_OFFSET default values

For platforms that are not yet converted to ARCH_MULTIPLATFORM, we can disable CONFIG_ARM_PATCH_PHYS_VIRT, which in turn requires setting a correct address here. As we actualy know what all the values are supposed to be based on the old mach/memory.h header file contents (from git history), we