Re: xtensa build failures in -next due to DMA API changes

Hi Andrew, Linus has merged the Xtensa patches, so you should be ready to go. Thanks, -Chris On Wed, Aug 26, 2015 at 10:41 AM, Christoph Hellwig wrote: > On Wed, Aug 26, 2015 at 10:53:25AM +0300, Max Filippov wrote: >> Looks like I just need to remove now redundant function definitions from >>

Re: xtensa build failures in -next due to DMA API changes

Hi Andrew, Linus has merged the Xtensa patches, so you should be ready to go. Thanks, -Chris On Wed, Aug 26, 2015 at 10:41 AM, Christoph Hellwig wrote: > On Wed, Aug 26, 2015 at 10:53:25AM +0300, Max Filippov wrote: >> Looks like I just need to remove now redundant function

Re: xtensa build failures in -next due to DMA API changes

I'll send the pull request as soon as possible. On Wed, Aug 26, 2015 at 12:59 AM, Andrew Morton wrote: > On Wed, 26 Aug 2015 10:53:25 +0300 Max Filippov wrote: > >> On Tue, Aug 25, 2015 at 11:24 PM, Christoph Hellwig wrote: >> > On Tue, Aug 25, 2015 at 01:21:40PM -0700, Guenter Roeck wrote: >>

Re: xtensa build failures in -next due to DMA API changes

I'll send the pull request as soon as possible. On Wed, Aug 26, 2015 at 12:59 AM, Andrew Morton a...@linux-foundation.org wrote: On Wed, 26 Aug 2015 10:53:25 +0300 Max Filippov jcmvb...@gmail.com wrote: On Tue, Aug 25, 2015 at 11:24 PM, Christoph Hellwig h...@lst.de wrote: On Tue, Aug 25,

Re: [PATCH v3] xtensa: improve vmlinux.lds.S sed post-processing

Thanks Max. Running a test build and will add to xtensa-next. On Fri, Aug 21, 2015 at 10:43 AM, Max Filippov wrote: > Current sed script makes assumptions about the structure of rules that > group .text sections in the vmlinux linker script. These assumptions > get broken occasionally, e.g.:

Re: [PATCH v3] xtensa: improve vmlinux.lds.S sed post-processing

Thanks Max. Running a test build and will add to xtensa-next. On Fri, Aug 21, 2015 at 10:43 AM, Max Filippov jcmvb...@gmail.com wrote: Current sed script makes assumptions about the structure of rules that group .text sections in the vmlinux linker script. These assumptions get broken

Re: [PATCH 2/8] xtensa: keep exception/interrupt stack continuous

Hi Max, Not such a big fan about these changes as they introduce additional load and stores and a branch. Copy spill area: - is this only for debugging? Could the debugger identify the 'kernel exception' frame and handle it appropriately? - if we need it for debugging/perf, maybe move these line

Re: [PATCH 2/8] xtensa: keep exception/interrupt stack continuous

Hi Max, Not such a big fan about these changes as they introduce additional load and stores and a branch. Copy spill area: - is this only for debugging? Could the debugger identify the 'kernel exception' frame and handle it appropriately? - if we need it for debugging/perf, maybe move these line

Re: [PATCH 7/8] xtensa: implement counting and sampling perf events

Hi Max, We could probably still use NMI with a separate stack. However, for exception handling while in NMI, we might have to implement something similar to x86_64 (https://lwn.net/Articles/484932/). Cheers! -Chris On Mon, Jul 6, 2015 at 7:22 AM, Max Filippov wrote: > On Mon, Jul 6, 2015 at

Re: [PATCH 7/8] xtensa: implement counting and sampling perf events

Hi Max, We could probably still use NMI with a separate stack. However, for exception handling while in NMI, we might have to implement something similar to x86_64 (https://lwn.net/Articles/484932/). Cheers! -Chris On Mon, Jul 6, 2015 at 7:22 AM, Max Filippov jcmvb...@gmail.com wrote: On Mon,

Re: [PATCH resend 3/5] xtensa: Provide dummy dma_alloc_attrs() and dma_free_attrs()

Hi Guenter, Sorry for the delay. Will work on it later today or tomorrow. Thanks, -Chris On Mon, May 4, 2015 at 3:30 PM, Guenter Roeck wrote: > xtensa:allmodconfig fails to build with the following errors. > > drivers/gpu/drm/nouveau/nvkm/subdev/instmem/gk20a.c: > In function

Re: [PATCH resend 3/5] xtensa: Provide dummy dma_alloc_attrs() and dma_free_attrs()

Hi Guenter, Sorry for the delay. Will work on it later today or tomorrow. Thanks, -Chris On Mon, May 4, 2015 at 3:30 PM, Guenter Roeck li...@roeck-us.net wrote: xtensa:allmodconfig fails to build with the following errors. drivers/gpu/drm/nouveau/nvkm/subdev/instmem/gk20a.c: In

Re: [PATCH -next] xtensa: Fix fix linker script transformation for .text / .text.fixup

On Wed, Apr 8, 2015 at 6:08 AM, Guenter Roeck wrote: > On 04/07/2015 11:14 PM, Max Filippov wrote: >>> Linker script transformation needs to be updated to detect and handle >>> the new section. >> I've posted a patch for it to the linux-xtensa ML a while ago: >>

Re: [PATCH -next] xtensa: Fix fix linker script transformation for .text / .text.fixup

On Wed, Apr 8, 2015 at 6:08 AM, Guenter Roeck li...@roeck-us.net wrote: On 04/07/2015 11:14 PM, Max Filippov wrote: Linker script transformation needs to be updated to detect and handle the new section. I've posted a patch for it to the linux-xtensa ML a while ago:

Re: [PATCH 2/2] xtensa/uapi: Add definition of TIOC[SG]RS485

Hi Ricardo, I'll add it to the xtensa-next tree today.. Thanks, -Chris On 9/9/14, 10:32 AM, Ricardo Ribalda Delgado wrote: Hello Max I really don't know who should do it, the maintainer of tty-next or you :). I guess Greg will want that his is fixed on his tree asap, since that build is

Re: [PATCH 2/2] xtensa/uapi: Add definition of TIOC[SG]RS485

Hi Ricardo, I'll add it to the xtensa-next tree today.. Thanks, -Chris On 9/9/14, 10:32 AM, Ricardo Ribalda Delgado wrote: Hello Max I really don't know who should do it, the maintainer of tty-next or you :). I guess Greg will want that his is fixed on his tree asap, since that build is

Re: CONFIG_SLUB/USE_SPLIT_PTLOCKS compatibility

On 10/14/2013 04:49 AM, Max Filippov wrote: > Buddy allocator was used here prior to commit 6656920 [XTENSA] Add > support for cache-aliasing I can only guess that the change was made > to make allocated page tables have the same colour, but am not sure > why this is needed. Chris? Max, I think

Re: CONFIG_SLUB/USE_SPLIT_PTLOCKS compatibility

On 10/14/2013 04:49 AM, Max Filippov wrote: Buddy allocator was used here prior to commit 6656920 [XTENSA] Add support for cache-aliasing I can only guess that the change was made to make allocated page tables have the same colour, but am not sure why this is needed. Chris? Max, I think you

Re: [PATCH] xtensa: Fix broken allmodconfig build

Hi Guenter, On 9/2/13 7:55 PM, Guenter Roeck wrote: On 08/27/2013 09:06 PM, Guenter Roeck wrote: xtansa allmodbuild fails with: arch/xtensa/kernel/xtensa_ksyms.c:129:1: error: '_mcount' undeclared here (not in a function) make[2]: *** [arch/xtensa/kernel/xtensa_ksyms.o] Error 1 make[1]: ***

Re: [PATCH] xtensa: Fix broken allmodconfig build

Hi Guenter, On 9/2/13 7:55 PM, Guenter Roeck wrote: On 08/27/2013 09:06 PM, Guenter Roeck wrote: xtansa allmodbuild fails with: arch/xtensa/kernel/xtensa_ksyms.c:129:1: error: '_mcount' undeclared here (not in a function) make[2]: *** [arch/xtensa/kernel/xtensa_ksyms.o] Error 1 make[1]: ***

Re: [PATCH] arch: xtensa: include: asm: define '_PAGE_CHG_MASK' when 'NOMMU'

Hi Chen, On 06/22/2013 12:46 AM, Chen Gang wrote: > After define it, with the same .config file, also report another errors > below, Did I use the incorrect cross-compiler tools ? It almost seems that you are not using the cross compiler. There are two ways to specify the cross compiler. 1. As

Re: [PATCH] arch: xtensa: include: asm: define '_PAGE_CHG_MASK' when 'NOMMU'

Hi Chen, On 06/22/2013 12:46 AM, Chen Gang wrote: After define it, with the same .config file, also report another errors below, Did I use the incorrect cross-compiler tools ? It almost seems that you are not using the cross compiler. There are two ways to specify the cross compiler. 1. As

[merged] Re: [PATCH 3/3] xtensa: Switch to asm-generic/linkage.h

Should make it to Linus' tree shortly. Thanks, -Chris On 05/07/2013 02:57 AM, Geert Uytterhoeven wrote: > Signed-off-by: Geert Uytterhoeven > --- > arch/xtensa/include/asm/Kbuild|1 + > arch/xtensa/include/asm/linkage.h | 16 > 2 files changed, 1 insertions(+), 16

[merged] Re: [PATCH 3/3] xtensa: Switch to asm-generic/linkage.h

Should make it to Linus' tree shortly. Thanks, -Chris On 05/07/2013 02:57 AM, Geert Uytterhoeven wrote: Signed-off-by: Geert Uytterhoeven ge...@linux-m68k.org --- arch/xtensa/include/asm/Kbuild|1 + arch/xtensa/include/asm/linkage.h | 16 2 files changed, 1

Re: [patch 00/34] idle: Consolidate idle implementations

Hi Thomas, On 3/28/13 2:24 AM, Thomas Gleixner wrote: On Thu, 28 Mar 2013, Chris Zankel wrote: For Xtensa: Acked-by: Chris Zankel Thanks for going the extra mile and test-compiling it. Though, the build fails later with: arch/xtensa/kernel/built-in.o:(.init.literal+0x90): undefined

Re: [patch 00/34] idle: Consolidate idle implementations

Hi Thomas, On 3/28/13 2:24 AM, Thomas Gleixner wrote: On Thu, 28 Mar 2013, Chris Zankel wrote: For Xtensa: Acked-by: Chris Zankel ch...@zankel.net Thanks for going the extra mile and test-compiling it. Though, the build fails later with: arch/xtensa/kernel/built-in.o:(.init.literal+0x90

[GIT PULL] xtensa changes for 3.9

Chris Zankel (2): xtensa: add support for TLS xtensa: add accept4 syscall Marc Gauthier (1): xtensa: dispatch medium-priority interrupts Max Filippov (10): xtensa: rename prom_update_property to of_update_property xtensa: fix

[GIT PULL] xtensa changes for 3.9

Chris Zankel (2): xtensa: add support for TLS xtensa: add accept4 syscall Marc Gauthier (1): xtensa: dispatch medium-priority interrupts Max Filippov (10): xtensa: rename prom_update_property to of_update_property xtensa: fix

Re: [PATCH REPOST] xtensa: use new common dtc rule

the new Makefile. Cc: Chris Zankel Cc: Max Filippov Cc: linux-xte...@linux-xtensa.org Signed-off-by: Stephen Warren --- This patch applies recent dtc-rule-related changes to the xtensa arch. They couldn't be applied along with the similar changes for other archs due to dependencies on other xtensa

Re: [PATCH REPOST] xtensa: use new common dtc rule

/Makefile to call the new Makefile. Cc: Chris Zankel ch...@zankel.net Cc: Max Filippov jcmvb...@gmail.com Cc: linux-xte...@linux-xtensa.org Signed-off-by: Stephen Warren swar...@nvidia.com --- This patch applies recent dtc-rule-related changes to the xtensa arch. They couldn't be applied along

Re: [digsig:dmi 20/35] WARNING: security/integrity/built-in.o(.text+0x1d8): Section mismatch in reference from the function integrity_inode_free() to the variable .init.data:ima_use_tcb

Pressed the 'send' button a bit too fast. On 11/07/2012 03:31 PM, Chris Zankel wrote: > Hi, > > Looking a bit into it, I think modpost is broken. I'm working on a fix. This is specific to Xtensa. Symbols are stored in a separate '.lit' section, but modpost doesn't seem to currentl

Re: [digsig:dmi 20/35] WARNING: security/integrity/built-in.o(.text+0x1d8): Section mismatch in reference from the function integrity_inode_free() to the variable .init.data:ima_use_tcb

Hi, Looking a bit into it, I think modpost is broken. I'm working on a fix. Cheers! -Chris On 11/06/2012 03:57 AM, Fengguang Wu wrote: > Perhaps we should CC more people.. > > On Tue, Nov 06, 2012 at 01:47:18PM +0200, Kasatkin, Dmitry wrote: >> On Tue, Nov 6, 2012 at 1:41 PM, Fengguang Wu

Re: [digsig:dmi 20/35] WARNING: security/integrity/built-in.o(.text+0x1d8): Section mismatch in reference from the function integrity_inode_free() to the variable .init.data:ima_use_tcb

Hi, Looking a bit into it, I think modpost is broken. I'm working on a fix. Cheers! -Chris On 11/06/2012 03:57 AM, Fengguang Wu wrote: Perhaps we should CC more people.. On Tue, Nov 06, 2012 at 01:47:18PM +0200, Kasatkin, Dmitry wrote: On Tue, Nov 6, 2012 at 1:41 PM, Fengguang Wu

Re: [digsig:dmi 20/35] WARNING: security/integrity/built-in.o(.text+0x1d8): Section mismatch in reference from the function integrity_inode_free() to the variable .init.data:ima_use_tcb

Pressed the 'send' button a bit too fast. On 11/07/2012 03:31 PM, Chris Zankel wrote: Hi, Looking a bit into it, I think modpost is broken. I'm working on a fix. This is specific to Xtensa. Symbols are stored in a separate '.lit' section, but modpost doesn't seem to currently resolve

[PULL REQUEST for 3.7-rc4 - second attempt] xtensa: fix syscall table and vfork, and switch to generic thread/execve

Chris Zankel (3): xtensa: allow multi-inclusion for uapi/unistd.h xtensa: use physical addresses for bus addresses xtensa: reset windowbase/windowstart when cloning the VM Max Filippov (3): xtensa: switch to generic

[PULL REQUEST for 3.7-rc4] xtensa: fix syscall table and vfork, and switch to generic thread/execve

to dc241f2c1761bfdec85915f4bbf7e750663f3442: xtensa: switch to generic sys_execve() (2012-10-25 15:00:44 -0700) Xtensa patchset for 3.7-rc4 Chris Zankel (3): xtensa: allow multi-inclusion for uapi

[PULL REQUEST for 3.7-rc4] xtensa: fix syscall table and vfork, and switch to generic thread/execve

to dc241f2c1761bfdec85915f4bbf7e750663f3442: xtensa: switch to generic sys_execve() (2012-10-25 15:00:44 -0700) Xtensa patchset for 3.7-rc4 Chris Zankel (3): xtensa: allow multi-inclusion for uapi

[PULL REQUEST for 3.7-rc4 - second attempt] xtensa: fix syscall table and vfork, and switch to generic thread/execve

Chris Zankel (3): xtensa: allow multi-inclusion for uapi/unistd.h xtensa: use physical addresses for bus addresses xtensa: reset windowbase/windowstart when cloning the VM Max Filippov (3): xtensa: switch to generic

Re: [ 60/85] xtensa: add missing system calls to the syscall table

Hi Ben, On 10/27/2012 11:26 AM, Ben Hutchings wrote: > On Thu, 2012-10-25 at 17:06 -0700, Greg Kroah-Hartman wrote: > [...] >> #define __NR_available287 287 >> -__SYSCALL(287, sys_faccessat, 0) >> +__SYSCALL(287, sys_ni_syscall, 0) > [...] > > Why was this one un-plumbed

Re: [ 60/85] xtensa: add missing system calls to the syscall table

Hi Ben, On 10/27/2012 11:26 AM, Ben Hutchings wrote: On Thu, 2012-10-25 at 17:06 -0700, Greg Kroah-Hartman wrote: [...] #define __NR_available287 287 -__SYSCALL(287, sys_faccessat, 0) +__SYSCALL(287, sys_ni_syscall, 0) [...] Why was this one un-plumbed rather than

[PATCH stable] xtensa: add missing system calls to the syscall table

Hi Greg, Could you please include this patch in the next stable tree? It adds system calls required for libc builds, so would be great to have it there. Thanks, -Chris From 72b843f6fa14a818a833625d78d8023828366bb1 Mon Sep 17 00:00:00 2001 From: Chris Zankel Date: Wed, 24 Oct 2012 12:59:28

[PATCH stable] xtensa: add missing system calls to the syscall table

Hi Greg, Could you please include this patch in the next stable tree? It adds system calls required for libc builds, so would be great to have it there. Thanks, -Chris From 72b843f6fa14a818a833625d78d8023828366bb1 Mon Sep 17 00:00:00 2001 From: Chris Zankel ch...@zankel.net Date: Wed, 24

Re: linux-next: manual merge of the xtensa tree with Linus' tree

Hi Stephen, Sorry, I accidentally pushed this patch up; should be fixed the next next time you pull. Thanks, -Chris On 10/21/2012 04:40 PM, Stephen Rothwell wrote: Hi Chris, Today's linux-next merge of the xtensa tree got a conflict in arch/xtensa/include/uapi/asm/unistd.h between commit

Re: linux-next: manual merge of the xtensa tree with Linus' tree

Hi Stephen, Sorry, I accidentally pushed this patch up; should be fixed the next next time you pull. Thanks, -Chris On 10/21/2012 04:40 PM, Stephen Rothwell wrote: Hi Chris, Today's linux-next merge of the xtensa tree got a conflict in arch/xtensa/include/uapi/asm/unistd.h between commit

[GIT PULL] xtensa patches

missing system calls to the syscall table (2012-10-19 10:46:44 -0700) Xtensa patchset for 3.7-rc2 Chris Zankel (3): xtensa: fix memmove(), bcopy(), and memcpy

[GIT PULL] xtensa patches

missing system calls to the syscall table (2012-10-19 10:46:44 -0700) Xtensa patchset for 3.7-rc2 Chris Zankel (3): xtensa: fix memmove(), bcopy(), and memcpy

Re: [ 103/133] xtensa: Add missing RCU idle APIs on idle loop

Hi Greg, Thanks for adding it. Signed-off-by: Chris Zankel On 10/10/2012 03:52 PM, Greg Kroah-Hartman wrote: 3.5-stable review patch. If anyone has any objections, please let me know. -- From: Frederic Weisbecker commit 11ad47a0edbd62bfc0547cfcdf227a911433f207 upstream

Re: [ 103/133] xtensa: Add missing RCU idle APIs on idle loop

Hi Greg, Thanks for adding it. Signed-off-by: Chris Zankel ch...@zankel.net On 10/10/2012 03:52 PM, Greg Kroah-Hartman wrote: 3.5-stable review patch. If anyone has any objections, please let me know. -- From: Frederic Weisbecker fweis...@gmail.com commit

[GIT PULL] xtensa patchset for 3.7

up to 70cefe765433529fc894fd1995a1d5883cb33e05: xtensa: Setup CROSS_COMPILE at the top (2012-10-04 12:16:20 -0700) Xtensa patchset for 3.7 ---- Chris Zankel (1): MAINTAINERS: add

[GIT PULL] xtensa patchset for 3.7

to 70cefe765433529fc894fd1995a1d5883cb33e05: xtensa: Setup CROSS_COMPILE at the top (2012-10-04 12:16:20 -0700) Xtensa patchset for 3.7 Chris Zankel (1): MAINTAINERS: add Max

Re: [GIT PULL] xtensa patchset for 3.7

wrote: Hi Chris, On Thu, Oct 4, 2012 at 12:23 AM, Chris Zankel wrote: Patchset for the Xtensa architecture for 3.7 I think you forgot https://lkml.org/lkml/2012/9/10/560 Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge

Re: [GIT PULL] xtensa patchset for 3.7

wrote: Hi Chris, On Thu, Oct 4, 2012 at 12:23 AM, Chris Zankel ch...@zankel.net wrote: Patchset for the Xtensa architecture for 3.7 I think you forgot https://lkml.org/lkml/2012/9/10/560 Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond

Re: [GIT PULL] xtensa patchset for 3.7

Hi Linus, On 10/03/2012 03:41 PM, Linus Torvalds wrote: That should be git://github.com/czankel/xtensa-linux tags/xtensa-next-20121003 which is the public git address of that server. Sorry about that. I mistakenly used 'origin' instead of the actual address. However, you now do have a

[GIT PULL] xtensa patchset for 3.7

Chris Zankel (1): MAINTAINERS: add Max Filippov as an xtensa port maintainer Max Filippov (25): xtensa: fix linker script transformation for .text.unlikely xtensa: ISS: only build networking if configured xtensa/PCI: fix WT caching

[GIT PULL] xtensa patchset for 3.7

Chris Zankel (1): MAINTAINERS: add Max Filippov as an xtensa port maintainer Max Filippov (25): xtensa: fix linker script transformation for .text.unlikely xtensa: ISS: only build networking if configured xtensa/PCI: fix WT caching

Re: [GIT PULL] xtensa patchset for 3.7

Hi Linus, On 10/03/2012 03:41 PM, Linus Torvalds wrote: That should be git://github.com/czankel/xtensa-linux tags/xtensa-next-20121003 which is the public git address of that server. Sorry about that. I mistakenly used 'origin' instead of the actual address. However, you now do have a

Re: xtensa port maintenance

Hi Arnd, Given the recent renewed push for Xtensa, I'll step in to feed the changes upstream. We might change that in future, though. Max has volunteered to help bring the Xtensa port up-to-date. Most of the recent development was done on outdated trees and never got submitted in true

Re: xtensa port maintenance

Hi Arnd, Given the recent renewed push for Xtensa, I'll step in to feed the changes upstream. We might change that in future, though. Max has volunteered to help bring the Xtensa port up-to-date. Most of the recent development was done on outdated trees and never got submitted in true

Re: xtensa port maintenance

Hi Max, On 08/07/2012 09:43 AM, Max Filippov wrote: On Tue, Aug 7, 2012 at 9:40 AM, Chris Zankel wrote: Hi Max, On 08/06/2012 04:38 PM, Max Filippov wrote: AFAIK xtensa linux port is currently in bad shape: it doesn't work in the mainline, it fails to build in the linux-next. The latest

Re: [Linux-Xtensa] Re: xtensa port maintenance

-linux on it. I propose doing the testing on this board and any other tasks / issues you think I can help, I'd be glad to. Excellent!! I'm looking forward to your help. -Chris Vadim. On Tue, Aug 7, 2012 at 8:40 AM, Chris Zankel <mailto:ch...@zankel.net>> wrote: Hi Max,

Re: [Linux-Xtensa] Re: xtensa port maintenance

-linux on it. I propose doing the testing on this board and any other tasks / issues you think I can help, I'd be glad to. Excellent!! I'm looking forward to your help. -Chris Vadim. On Tue, Aug 7, 2012 at 8:40 AM, Chris Zankel ch...@zankel.net mailto:ch...@zankel.net wrote: Hi Max

Re: xtensa port maintenance

Hi Max, On 08/07/2012 09:43 AM, Max Filippov wrote: On Tue, Aug 7, 2012 at 9:40 AM, Chris Zankel ch...@zankel.net wrote: Hi Max, On 08/06/2012 04:38 PM, Max Filippov wrote: AFAIK xtensa linux port is currently in bad shape: it doesn't work in the mainline, it fails to build in the linux-next

Re: xtensa port maintenance

Hi Max, On 08/06/2012 04:38 PM, Max Filippov wrote: AFAIK xtensa linux port is currently in bad shape: it doesn't work in the mainline, it fails to build in the linux-next. The latest working kernels for xtensa are 2.6.29...31 trees hosted at the git.linux-xtensa.org. I wouldn't say it's in bad

Re: xtensa port maintenance

Hi Max, On 08/06/2012 04:38 PM, Max Filippov wrote: AFAIK xtensa linux port is currently in bad shape: it doesn't work in the mainline, it fails to build in the linux-next. The latest working kernels for xtensa are 2.6.29...31 trees hosted at the git.linux-xtensa.org. I wouldn't say it's in bad

Re: git-xtensa doesn't like my cross compiler

Hi Adrian, Thanks for pointing this out. I'm working on a fix. BTW, which branch do you use? release or testing? Thanks, -CHris Adrian Bunk wrote: With git-xtensa I'm getting: <-- snip --> ... /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/xtensa/Makefile:30: *** No Xtensa toolchain

Re: git-xtensa doesn't like my cross compiler

Hi Adrian, Thanks for pointing this out. I'm working on a fix. BTW, which branch do you use? release or testing? Thanks, -CHris Adrian Bunk wrote: With git-xtensa I'm getting: -- snip -- ... /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/xtensa/Makefile:30: *** No Xtensa toolchain found

Re: [PATCH] fix modpost warnings for xtensa

Andrew, Andrew Morton wrote: This generates unfixable-by-me rejects against Sam's git-kbuild tree. Sam already had a pull request into Linus for that tree. Could I ask that you wait for that piece of dust to settle and then regenerate the diff? Thanks Andrew. I will wait for his updates.

[PATCH] fix modpost warnings for xtensa

regressions for other architectures. We also need to suppress warnings for two informational sections (.xt.lit and .xt.prop) used by the Xtensa architecture. Signed-off-by: Chris Zankel <[EMAIL PROTECTED]> diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c index 3

[PATCH] fix modpost warnings for xtensa

regressions for other architectures. We also need to suppress warnings for two informational sections (.xt.lit and .xt.prop) used by the Xtensa architecture. Signed-off-by: Chris Zankel [EMAIL PROTECTED] diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c index 3645e98

Re: [PATCH] fix modpost warnings for xtensa

Andrew, Andrew Morton wrote: This generates unfixable-by-me rejects against Sam's git-kbuild tree. Sam already had a pull request into Linus for that tree. Could I ask that you wait for that piece of dust to settle and then regenerate the diff? Thanks Andrew. I will wait for his updates.

Re: [PATCH] cross-architecture ELF clean up

Jeremy, Could you please add the ELF architecture-magic number for Xtensa (94) when you finally submit this patch? Jeremy Fitzhardinge wrote: This patch cleans up the ELF headers and their users. It does several related things: --- /dev/null +++ b/include/linux/elf-const.h @@ -0,0 +1,222 @@

Re: [PATCH] cross-architecture ELF clean up

Jeremy, Could you please add the ELF architecture-magic number for Xtensa (94) when you finally submit this patch? Jeremy Fitzhardinge wrote: This patch cleans up the ELF headers and their users. It does several related things: --- /dev/null +++ b/include/linux/elf-const.h @@ -0,0 +1,222 @@

Re: We also need to get rid of verify_area in entry.S

Jesper, Thanks for the patches. I'll take a look at the entry.S one and will pass it along to Andres, and will incorporate the signal.c patch. I am currently working on the system call interface and am removing the non-rt signal calls, so the signal.c patch probably doesn't apply cleanly

Re: We also need to get rid of verify_area in entry.S

Jesper, Thanks for the patches. I'll take a look at the entry.S one and will pass it along to Andres, and will incorporate the signal.c patch. I am currently working on the system call interface and am removing the non-rt signal calls, so the signal.c patch probably doesn't apply cleanly