On Fri, Jan 29, 2016 at 10:54:02PM +0100, Arnd Bergmann wrote:
> Now that I think about it, I guess platforms that use values above
> 0xfee0 can also easily get into trouble as that conflicts with the
> PCI I/O space, the fixmap or other special areas documented in
>
On Friday 29 January 2016 22:24:31 Geert Uytterhoeven wrote:
> > diff --git a/arch/arm/include/debug/8250.S b/arch/arm/include/debug/8250.S
> > index 7f7446f6f806..1191b1458586 100644
> > --- a/arch/arm/include/debug/8250.S
> > +++ b/arch/arm/include/debug/8250.S
> > @@ -9,6 +9,9 @@
> > */
> >
On Fri, Jan 29, 2016 at 12:07:21AM +0100, Arnd Bergmann wrote:
> This doesn't sound too hard. I've picked the defaults out of the
> git history in the patch below. The only tricky part was davinci,
> which has two different addresses and requires a little rework
> to avoid circular dependencies.
Hi Arnd,
On Fri, Jan 29, 2016 at 9:44 PM, Arnd Bergmann wrote:
>
> diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
> index c6b6175d0203..6cc09cf8618f 100644
> --- a/arch/arm/Kconfig.debug
> +++ b/arch/arm/Kconfig.debug
> @@ -1526,6 +1526,7 @@ config DEBUG_UART_PHYS
> default
On Friday 29 January 2016 09:01:31 Geert Uytterhoeven wrote:
> Hi Arnd,
>
> On Fri, Jan 29, 2016 at 12:07 AM, Arnd Bergmann wrote:
> > The other related issue is the DEBUG_UART_{VIRT,PHYS} setting,
> > where there is no safe platform-specific default. I have two
> > ideas for working around
Hi Arnd,
On Fri, Jan 29, 2016 at 12:07 AM, Arnd Bergmann wrote:
> The other related issue is the DEBUG_UART_{VIRT,PHYS} setting,
> where there is no safe platform-specific default. I have two
> ideas for working around that, maybe one of them sounds ok to
> you:
>
> a) find a way to warn and/or
Hi Arnd,
On Fri, Jan 29, 2016 at 12:07 AM, Arnd Bergmann wrote:
> The other related issue is the DEBUG_UART_{VIRT,PHYS} setting,
> where there is no safe platform-specific default. I have two
> ideas for working around that, maybe one of them sounds ok to
> you:
>
> a) find a way
On Fri, Jan 29, 2016 at 10:54:02PM +0100, Arnd Bergmann wrote:
> Now that I think about it, I guess platforms that use values above
> 0xfee0 can also easily get into trouble as that conflicts with the
> PCI I/O space, the fixmap or other special areas documented in
>
On Friday 29 January 2016 22:24:31 Geert Uytterhoeven wrote:
> > diff --git a/arch/arm/include/debug/8250.S b/arch/arm/include/debug/8250.S
> > index 7f7446f6f806..1191b1458586 100644
> > --- a/arch/arm/include/debug/8250.S
> > +++ b/arch/arm/include/debug/8250.S
> > @@ -9,6 +9,9 @@
> > */
> >
On Fri, Jan 29, 2016 at 12:07:21AM +0100, Arnd Bergmann wrote:
> This doesn't sound too hard. I've picked the defaults out of the
> git history in the patch below. The only tricky part was davinci,
> which has two different addresses and requires a little rework
> to avoid circular dependencies.
On Friday 29 January 2016 09:01:31 Geert Uytterhoeven wrote:
> Hi Arnd,
>
> On Fri, Jan 29, 2016 at 12:07 AM, Arnd Bergmann wrote:
> > The other related issue is the DEBUG_UART_{VIRT,PHYS} setting,
> > where there is no safe platform-specific default. I have two
> > ideas for
Hi Arnd,
On Fri, Jan 29, 2016 at 9:44 PM, Arnd Bergmann wrote:
>
> diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
> index c6b6175d0203..6cc09cf8618f 100644
> --- a/arch/arm/Kconfig.debug
> +++ b/arch/arm/Kconfig.debug
> @@ -1526,6 +1526,7 @@ config DEBUG_UART_PHYS
>
On Thursday 28 January 2016 17:42:41 you wrote:
> On Thu, Jan 28, 2016 at 11:14:35AM +0800, Fengguang Wu wrote:
> > On Wed, Jan 27, 2016 at 10:44:01AM +0100, Arnd Bergmann wrote:
> > > - CONFIG_PHYS_OFFSET needs to be entered manually to be a number
> > > in 'make config'
> >
> > That's a
Hi Arnd,
On Wed, Jan 27, 2016 at 10:44 AM, Arnd Bergmann wrote:
> - in some configurations, you end up without any boards selected, hitting
> an #error in the final link
FWIW, I have a similar problem with m68k+MMU=y randconfig...
Gr{oetje,eeting}s,
Geert
--
Geert
On Thu, Jan 28, 2016 at 11:14:35AM +0800, Fengguang Wu wrote:
> On Wed, Jan 27, 2016 at 10:44:01AM +0100, Arnd Bergmann wrote:
> > - CONFIG_PHYS_OFFSET needs to be entered manually to be a number
> > in 'make config'
>
> That's a problem for auto tests.
I'm really against the idea of providing
On Thursday 28 January 2016 11:14:35 Fengguang Wu wrote:
> > - CONFIG_PHYS_OFFSET needs to be entered manually to be a number
> > in 'make config'
>
> That's a problem for auto tests.
Ok, I'll try to revisit this one. Maybe I can turn it into a
'default 0x' with a compile-time
On Thursday 28 January 2016 17:42:41 you wrote:
> On Thu, Jan 28, 2016 at 11:14:35AM +0800, Fengguang Wu wrote:
> > On Wed, Jan 27, 2016 at 10:44:01AM +0100, Arnd Bergmann wrote:
> > > - CONFIG_PHYS_OFFSET needs to be entered manually to be a number
> > > in 'make config'
> >
> > That's a
On Thu, Jan 28, 2016 at 11:14:35AM +0800, Fengguang Wu wrote:
> On Wed, Jan 27, 2016 at 10:44:01AM +0100, Arnd Bergmann wrote:
> > - CONFIG_PHYS_OFFSET needs to be entered manually to be a number
> > in 'make config'
>
> That's a problem for auto tests.
I'm really against the idea of providing
On Thursday 28 January 2016 11:14:35 Fengguang Wu wrote:
> > - CONFIG_PHYS_OFFSET needs to be entered manually to be a number
> > in 'make config'
>
> That's a problem for auto tests.
Ok, I'll try to revisit this one. Maybe I can turn it into a
'default 0x' with a compile-time
Hi Arnd,
On Wed, Jan 27, 2016 at 10:44 AM, Arnd Bergmann wrote:
> - in some configurations, you end up without any boards selected, hitting
> an #error in the final link
FWIW, I have a similar problem with m68k+MMU=y randconfig...
Gr{oetje,eeting}s,
On Wed, Jan 27, 2016 at 10:44:01AM +0100, Arnd Bergmann wrote:
> On Wednesday 27 January 2016 17:30:18 Fengguang Wu wrote:
>
> > > Looks good, I'm just unsure about "multi_v8_defconfig", this does not
> > > exist. Do you mean multi_v5_defconfig?
>
> > Ah yes, multi_v8_defconfig does not exist
On Wednesday 27 January 2016 17:30:18 Fengguang Wu wrote:
> > Looks good, I'm just unsure about "multi_v8_defconfig", this does not
> > exist. Do you mean multi_v5_defconfig?
> Ah yes, multi_v8_defconfig does not exist actually.
Ok, can you include multi_v5_defconfig than?
I see you have one
On Wed, Jan 27, 2016 at 10:11:47AM +0100, Arnd Bergmann wrote:
> On Wednesday 27 January 2016 16:37:45 Fengguang Wu wrote:
> >
> > Thank you for the tips! I've updated the lists accordingly.
> >
> > 1st priority
> >
> >
> > arm-allmodconfig
> > arm-allnoconfig
> >
On Wednesday 27 January 2016 16:37:45 Fengguang Wu wrote:
>
> Thank you for the tips! I've updated the lists accordingly.
>
> 1st priority
>
>
> arm-allmodconfig
> arm-allnoconfig
> arm-at91_dt_defconfig
> arm-efm32_defconfig
> arm-exynos_defconfig
> arm-multi_v7_defconfig
>
Hi Arnd,
Thank you for the tips! I've updated the lists accordingly.
1st priority
arm-allmodconfig
arm-allnoconfig
arm-at91_dt_defconfig
arm-efm32_defconfig
arm-exynos_defconfig
arm-multi_v7_defconfig
arm-multi_v8_defconfig
arm-shmobile_defconfig
arm-sunxi_defconfig
2nd priority
On Wed, Jan 27, 2016 at 10:44:01AM +0100, Arnd Bergmann wrote:
> On Wednesday 27 January 2016 17:30:18 Fengguang Wu wrote:
>
> > > Looks good, I'm just unsure about "multi_v8_defconfig", this does not
> > > exist. Do you mean multi_v5_defconfig?
>
> > Ah yes, multi_v8_defconfig does not exist
Hi Arnd,
Thank you for the tips! I've updated the lists accordingly.
1st priority
arm-allmodconfig
arm-allnoconfig
arm-at91_dt_defconfig
arm-efm32_defconfig
arm-exynos_defconfig
arm-multi_v7_defconfig
arm-multi_v8_defconfig
arm-shmobile_defconfig
arm-sunxi_defconfig
2nd priority
On Wed, Jan 27, 2016 at 10:11:47AM +0100, Arnd Bergmann wrote:
> On Wednesday 27 January 2016 16:37:45 Fengguang Wu wrote:
> >
> > Thank you for the tips! I've updated the lists accordingly.
> >
> > 1st priority
> >
> >
> > arm-allmodconfig
> > arm-allnoconfig
> >
On Wednesday 27 January 2016 16:37:45 Fengguang Wu wrote:
>
> Thank you for the tips! I've updated the lists accordingly.
>
> 1st priority
>
>
> arm-allmodconfig
> arm-allnoconfig
> arm-at91_dt_defconfig
> arm-efm32_defconfig
> arm-exynos_defconfig
> arm-multi_v7_defconfig
>
On Wednesday 27 January 2016 17:30:18 Fengguang Wu wrote:
> > Looks good, I'm just unsure about "multi_v8_defconfig", this does not
> > exist. Do you mean multi_v5_defconfig?
> Ah yes, multi_v8_defconfig does not exist actually.
Ok, can you include multi_v5_defconfig than?
I see you have one
On Tuesday 26 January 2016 13:35:04 Fengguang Wu wrote:
> > There are a fixed set of config files for fast build tests (which I
> > selected randomly, feel free to ask me to change the list to more
> > reasonable ones):
> >
> > arm-allnoconfig
> > arm-at91_dt_defconfig
> >
On Tuesday 26 January 2016 13:35:04 Fengguang Wu wrote:
> > There are a fixed set of config files for fast build tests (which I
> > selected randomly, feel free to ask me to change the list to more
> > reasonable ones):
> >
> > arm-allnoconfig
> > arm-at91_dt_defconfig
> >
On Tue, Jan 26, 2016 at 01:30:50PM +0800, Fengguang Wu wrote:
> Hi Arnd,
>
> Sorry for the delay! I lost access to my email account for some week.
>
> On Tue, Jan 19, 2016 at 03:26:16PM +0100, Arnd Bergmann wrote:
> > On Tuesday 19 January 2016 19:27:55 kbuild test robot wrote:
> > > arm
Hi Arnd,
Sorry for the delay! I lost access to my email account for some week.
On Tue, Jan 19, 2016 at 03:26:16PM +0100, Arnd Bergmann wrote:
> On Tuesday 19 January 2016 19:27:55 kbuild test robot wrote:
> > arm allnoconfig
> > arm
Hi Arnd,
Sorry for the delay! I lost access to my email account for some week.
On Tue, Jan 19, 2016 at 03:26:16PM +0100, Arnd Bergmann wrote:
> On Tuesday 19 January 2016 19:27:55 kbuild test robot wrote:
> > arm allnoconfig
> > arm
On Tue, Jan 26, 2016 at 01:30:50PM +0800, Fengguang Wu wrote:
> Hi Arnd,
>
> Sorry for the delay! I lost access to my email account for some week.
>
> On Tue, Jan 19, 2016 at 03:26:16PM +0100, Arnd Bergmann wrote:
> > On Tuesday 19 January 2016 19:27:55 kbuild test robot wrote:
> > > arm
36 matches
Mail list logo