kisskb: OK linus/axs103_smp_defconfig/arcv2 Fri Oct 28, 05:39

2016-10-27 Thread noreply
OK linus/axs103_smp_defconfig/arcv2 Fri Oct 28, 05:39 http://kisskb.ellerman.id.au/kisskb/buildresult/12843293/ Commit: Merge branch 'for-linus' of git://git.kernel.dk/linux-block 9c953d639c2fb97e4e96f7398acbf4b675713b76 Compiler: arc-linux-gcc.br_real (Buildroot 2016.11-git-00613-ge9

Re: Build regressions/improvements in v4.9-rc1

2016-10-27 Thread Vineet Gupta
+CC Claudiu On 10/27/2016 02:39 AM, Alexey Brodkin wrote: > > And these are functions required by U-Boot (most probably the same is applied > to kernel): > 1) so-called millicode, stuff like __ld_rX_to_rY, __st_rX_to_rX This kicks in only at -Os and even there can be inhibited with a toggle. I d

Re: [PATCH v2] dmaengine: DW DMAC: split pdata to hardware properties and platform quirks

2016-10-27 Thread Andy Shevchenko
On Thu, 2016-10-27 at 18:34 +0300, Eugeniy Paltsev wrote: > This patch is to address a proposal by Andy in this thread: > http://www.spinics.net/lists/dmaengine/msg11506.html > Split platform data to actual hardware properties, and platform > quirks. > Now we able to use quirks and hardware propert

[PATCH v2] dmaengine: DW DMAC: split pdata to hardware properties and platform quirks

2016-10-27 Thread Eugeniy Paltsev
This patch is to address a proposal by Andy in this thread: http://www.spinics.net/lists/dmaengine/msg11506.html Split platform data to actual hardware properties, and platform quirks. Now we able to use quirks and hardware properties separately from different sources (pdata, device tree or autocon

Re: Build regressions/improvements in v4.9-rc1

2016-10-27 Thread Thomas Petazzoni
Hello, On Thu, 27 Oct 2016 09:07:55 +, Alexey Brodkin wrote: > > axs101 is using a 770 core, while the toolchain is built for the HS38 > > core. I'm somewhat surprised that a single ARC toolchain cannot produce > > code for both 770 and HS38, but it seems to be the case. > > > > So you need

Re: Build regressions/improvements in v4.9-rc1

2016-10-27 Thread Alexey Brodkin
Hi Thomas, On Thu, 2016-10-27 at 11:24 +0200, Geert Uytterhoeven wrote: > On Thu, Oct 27, 2016 at 11:11 AM, Thomas Petazzoni > wrote: > > > > On Thu, 27 Oct 2016 09:07:55 +, Alexey Brodkin wrote: > > > > > > > > > > > > > axs101 is using a 770 core, while the toolchain is built for the HS

Re: Build regressions/improvements in v4.9-rc1

2016-10-27 Thread Alexey Brodkin
Hi Thomas, Michael, On Thu, 2016-10-27 at 09:07 +0200, Thomas Petazzoni wrote: > Hello, > > On Thu, 27 Oct 2016 10:56:02 +1100, Michael Ellerman wrote: > > > > > > > > > Hm... that's strange - it used to work but doesn't work with newer > > > Buildroot... > > > > > > Anyways if something ver

Re: Build regressions/improvements in v4.9-rc1

2016-10-27 Thread Arnd Bergmann
On Thursday, October 27, 2016 11:11:18 AM CEST Thomas Petazzoni wrote: > On Thu, 27 Oct 2016 09:07:55 +, Alexey Brodkin wrote: > > > > axs101 is using a 770 core, while the toolchain is built for the HS38 > > > core. I'm somewhat surprised that a single ARC toolchain cannot produce > > > code

Re: Build regressions/improvements in v4.9-rc1

2016-10-27 Thread Thomas Petazzoni
Hello, On Thu, 27 Oct 2016 11:32:11 +0200, Arnd Bergmann wrote: > A couple of other architectures do this as well: > > $ git grep -w LIBGCC arch/*/Makefile > arch/arc/Makefile:LIBGCC:= $(shell $(CC) $(cflags-y) > --print-libgcc-file-name) > arch/arc/Makefile:libs-y+= arc

Re: Build regressions/improvements in v4.9-rc1

2016-10-27 Thread Geert Uytterhoeven
On Thu, Oct 27, 2016 at 11:11 AM, Thomas Petazzoni wrote: > On Thu, 27 Oct 2016 09:07:55 +, Alexey Brodkin wrote: > >> > axs101 is using a 770 core, while the toolchain is built for the HS38 >> > core. I'm somewhat surprised that a single ARC toolchain cannot produce >> > code for both 770 and

Re: Build regressions/improvements in v4.9-rc1

2016-10-27 Thread Thomas Petazzoni
Hello, On Thu, 27 Oct 2016 10:56:02 +1100, Michael Ellerman wrote: > > Hm... that's strange - it used to work but doesn't work with newer > > Buildroot... > > > > Anyways if something very simple (i.e. with no extra libraries) works for > > you just go > > ahead and grab pre-built image that Th