dma_alloc_coherent fails
Hi, Am using a linux 2.6.19 kernel for arm. the dma_alloc_coherent function call in the kernel for 38400 bytes fails. Has anyone faced this problem before?. What could be make dma_alloc_coherent to success sometimes and fail sometimes?. Regards, John - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
dma_alloc_coherent fails
Hi, Am using a linux 2.6.19 kernel for arm. the dma_alloc_coherent function call in the kernel for 38400 bytes fails. Has anyone faced this problem before?. What could be make dma_alloc_coherent to success sometimes and fail sometimes?. Regards, John - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
MTD - Linux Nand Driver problems
Hi, Im using Linux Kernel 2.6.18. Im using a large nand page device. In my device nand starts from 0x8 offset of nand. My kernel is around 1MB, I have allocated 2 MB space in my mtd partition structure. Similarly My Filesystem starts from 0x28 offset of nand. MY erase block size is 0x2 (128 KB) mkfs.jffs2 -p -l --eraseblock=128KiB -n -v -r ./rootfs -o /tmp/rootfs.jffs2 When boot my system i get hundreds of messages like: Empty flash at 0x02327ffc ends at 0x02328000 Empty flash at 0x0232fffc ends at 0x0233 Empty flash at 0x02337ffc ends at 0x02338000 Empty flash at 0x02347ffc ends at 0x02348000 Empty flash at 0x0234fffc ends at 0x0235 Empty flash at 0x02357ffc ends at 0x02358000 Empty flash at 0x02367ffc ends at 0x02368000 Empty flash at 0x0236fffc ends at 0x0237 Empty flash at 0x02377ffc ends at 0x02378000 Empty flash at 0x0238fffc ends at 0x0239 Empty flash at 0x023a7ffc ends at 0x023a8000 Empty flash at 0x023cfffc ends at 0x023d Empty flash at 0x023f7ffc ends at 0x023f8000 Empty flash at 0x02407ffc ends at 0x02408000 Empty flash at 0x02417ffc ends at 0x02418000 Empty flash at 0x0242fffc ends at 0x0243 Empty flash at 0x02447ffc ends at 0x02448000 Empty flash at 0x02477ffc ends at 0x02478000 Empty flash at 0x024a7ffc ends at 0x024a8000 Empty flash at 0x02527ffc ends at 0x02528000 Empty flash at 0x0252ffac ends at 0x0253 Empty flash at 0x02531abc ends at 0x02532000 I know the flash is empty - How does one prevent these messages at boot time. Regards, Jo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
MTD - Linux Nand Driver problems
Hi, Im using Linux Kernel 2.6.18. Im using a large nand page device. In my device nand starts from 0x8 offset of nand. My kernel is around 1MB, I have allocated 2 MB space in my mtd partition structure. Similarly My Filesystem starts from 0x28 offset of nand. MY erase block size is 0x2 (128 KB) mkfs.jffs2 -p -l --eraseblock=128KiB -n -v -r ./rootfs -o /tmp/rootfs.jffs2 When boot my system i get hundreds of messages like: Empty flash at 0x02327ffc ends at 0x02328000 Empty flash at 0x0232fffc ends at 0x0233 Empty flash at 0x02337ffc ends at 0x02338000 Empty flash at 0x02347ffc ends at 0x02348000 Empty flash at 0x0234fffc ends at 0x0235 Empty flash at 0x02357ffc ends at 0x02358000 Empty flash at 0x02367ffc ends at 0x02368000 Empty flash at 0x0236fffc ends at 0x0237 Empty flash at 0x02377ffc ends at 0x02378000 Empty flash at 0x0238fffc ends at 0x0239 Empty flash at 0x023a7ffc ends at 0x023a8000 Empty flash at 0x023cfffc ends at 0x023d Empty flash at 0x023f7ffc ends at 0x023f8000 Empty flash at 0x02407ffc ends at 0x02408000 Empty flash at 0x02417ffc ends at 0x02418000 Empty flash at 0x0242fffc ends at 0x0243 Empty flash at 0x02447ffc ends at 0x02448000 Empty flash at 0x02477ffc ends at 0x02478000 Empty flash at 0x024a7ffc ends at 0x024a8000 Empty flash at 0x02527ffc ends at 0x02528000 Empty flash at 0x0252ffac ends at 0x0253 Empty flash at 0x02531abc ends at 0x02532000 I know the flash is empty - How does one prevent these messages at boot time. Regards, Jo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Porting V4L2 drivers to 2.6.20
Hey, am porting V4L2 drivers from 2.6.13 to 2.6.20. The driver is using a structure 'video_device' which exists in include/linux/videodev.h. However, The linux kernel in 2.6.20 doesnot have that structure?. Has the architecture changed between 2.6.13 to 2.6.20 for V4L2?. Regards, Jo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Porting V4L2 drivers to 2.6.20
Hey, am porting V4L2 drivers from 2.6.13 to 2.6.20. The driver is using a structure 'video_device' which exists in include/linux/videodev.h. However, The linux kernel in 2.6.20 doesnot have that structure?. Has the architecture changed between 2.6.13 to 2.6.20 for V4L2?. Regards, Jo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: irqdesc porting help
Hi, Sorry for the late response, attached is the code im trying to port to linux - 2.6.20. Regards, Jo On 2/15/07, Paul Mundt <[EMAIL PROTECTED]> wrote: On Thu, Feb 15, 2007 at 12:01:37PM +0530, Maximus wrote: > Im trying to port some drivers between 2.6.14 and 2.6.19 > > I find that irqdesc has changed completely. how do i port > the drivers between 2.6.14 and 2.6.19? > > is there a porting guide available to port the drivers > which use irqdesc?. > > my drivers use variables triggered, ... which dont exist in 2.6.19 > irqdesc strcuture. > Presumably you're talking about the struct hw_interrupt_type and the lack of an irq_desc[irq].handler? There's some migration helper glue in include/linux/irq.h that you can use, but you're better off converting completely. You can at least get it building again by changing to irq_desc[irq].chip, but you really want a proper irq_chip implementation to go along with this, rather than munging in the hw_interrupt_type. You can easily compare before-and-after versions of most of the IRQ controllers to identify the minimal changes required. /* * linux/drivers/i2c/chips/twl4030_core.c * * Copyright (C) 2005-2006 Texas Instruments, Inc. * * Modifications to defer interrupt handling to a kernel thread: * Copyright (C) 2006 MontaVista Software, Inc. * * Based on tlv320aic23.c: * Copyright (c) by Kai Svahn <[EMAIL PROTECTED]> * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation; either version 2 of the License, or * (at your option) any later version. * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. * * You should have received a copy of the GNU General Public License * along with this program; if not, write to the Free Software * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA * */ /*** Includes */ #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include //#include #include #include #include #include #define CONFIG_TWL4030_IRQ_PRIO 26 / Macro Definitions */ #define TWL_CLIENT_STRING"TWL4030-ID" #define TWL_CLIENT_USED 1 #define TWL_CLIENT_FREE 0 /* IRQ Flags */ #define FREE 0 #define USED 1 /** Primary Interrupt Handler on TWL4030 Registers */ / Register Definitions */ #define REG_PIH_ISR_P1 (0x1) #define REG_PIH_ISR_P2 (0x2) #define REG_PIH_SIR (0x3) / BitField Definitions */ /* PIH_ISR_P1 Fields */ #define BIT_PIH_ISR_P1_PIH_ISR0 (0x000) #define BIT_PIH_ISR_P1_PIH_ISR0_M(0x0001) #define BIT_PIH_ISR_P1_PIH_ISR1 (0x001) #define BIT_PIH_ISR_P1_PIH_ISR1_M(0x0002) #define BIT_PIH_ISR_P1_PIH_ISR2 (0x002) #define BIT_PIH_ISR_P1_PIH_ISR2_M(0x0004) #define BIT_PIH_ISR_P1_PIH_ISR3 (0x003) #define BIT_PIH_ISR_P1_PIH_ISR3_M(0x0008) #define BIT_PIH_ISR_P1_PIH_ISR4 (0x004) #define BIT_PIH_ISR_P1_PIH_ISR4_M(0x0010) #define BIT_PIH_ISR_P1_PIH_ISR5 (0x005) #define BIT_PIH_ISR_P1_PIH_ISR5_M(0x0020) #define BIT_PIH_ISR_P1_PIH_ISR6 (0x006) #define BIT_PIH_ISR_P1_PIH_ISR6_M(0x0040) #define BIT_PIH_ISR_P1_PIH_ISR7 (0x007) #define BIT_PIH_ISR_P1_PIH_ISR7_M(0x0080) /* PIH_ISR_P2 Fields */ #define BIT_PIH_ISR_P2_PIH_ISR0 (0x000) #define BIT_PIH_ISR_P2_PIH_ISR0_M(0x0001) #define BIT_PIH_ISR_P2_PIH_ISR1 (0x001) #define BIT_PIH_ISR_P2_PIH_ISR1_M(0x0002) #define BIT_PIH_ISR_P2_PIH_ISR2 (0x002) #define BIT_PIH_ISR_P2_PIH_ISR2_M(0x0004) #define BIT_PIH_ISR_P2_PIH_ISR3 (0x003) #define BIT_PIH_ISR_P2_PIH_ISR3_M(0x0008) #define BIT_PIH_ISR_P2_PIH_ISR4 (0x004) #define BIT_PIH_ISR_P2_PIH_ISR4_M(0x0010) #define BIT_PIH_ISR_P2_PIH_ISR5 (0x005) #define BIT_PIH_ISR_P2_PIH_ISR5_M(0x0020) #define BIT_PIH_ISR_P2_PIH_ISR6 (0x006) #define BIT_PIH_ISR_P2_PIH_ISR6_M(0x0040) #define BIT_PIH_ISR_P2_PIH_ISR7 (0x007) #define BIT_PIH_ISR_P2_PIH_ISR7_M(0x000
Re: irqdesc porting help
Hi, Sorry for the late response, attached is the code im trying to port to linux - 2.6.20. Regards, Jo On 2/15/07, Paul Mundt [EMAIL PROTECTED] wrote: On Thu, Feb 15, 2007 at 12:01:37PM +0530, Maximus wrote: Im trying to port some drivers between 2.6.14 and 2.6.19 I find that irqdesc has changed completely. how do i port the drivers between 2.6.14 and 2.6.19? is there a porting guide available to port the drivers which use irqdesc?. my drivers use variables triggered, ... which dont exist in 2.6.19 irqdesc strcuture. Presumably you're talking about the struct hw_interrupt_type and the lack of an irq_desc[irq].handler? There's some migration helper glue in include/linux/irq.h that you can use, but you're better off converting completely. You can at least get it building again by changing to irq_desc[irq].chip, but you really want a proper irq_chip implementation to go along with this, rather than munging in the hw_interrupt_type. You can easily compare before-and-after versions of most of the IRQ controllers to identify the minimal changes required. /* * linux/drivers/i2c/chips/twl4030_core.c * * Copyright (C) 2005-2006 Texas Instruments, Inc. * * Modifications to defer interrupt handling to a kernel thread: * Copyright (C) 2006 MontaVista Software, Inc. * * Based on tlv320aic23.c: * Copyright (c) by Kai Svahn [EMAIL PROTECTED] * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation; either version 2 of the License, or * (at your option) any later version. * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. * * You should have received a copy of the GNU General Public License * along with this program; if not, write to the Free Software * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA * */ /*** Includes */ #include linux/config.h #include linux/module.h #include linux/kernel_stat.h #include linux/init.h #include linux/time.h #include linux/interrupt.h #include linux/random.h #include linux/syscalls.h #include linux/kthread.h #include linux/i2c.h #include linux/slab.h #include asm/arch/twl4030.h #include asm/arch/irqs.h #include asm/irq.h #include asm/arch/irq.h #include asm/mach/irq.h #include asm/arch/gpio.h //#include asm/arch/platform.h #include asm/arch/mux.h #include asm/arch/power_companion.h #include linux/device.h #include asm/arch/bus.h #define CONFIG_TWL4030_IRQ_PRIO 26 / Macro Definitions */ #define TWL_CLIENT_STRINGTWL4030-ID #define TWL_CLIENT_USED 1 #define TWL_CLIENT_FREE 0 /* IRQ Flags */ #define FREE 0 #define USED 1 /** Primary Interrupt Handler on TWL4030 Registers */ / Register Definitions */ #define REG_PIH_ISR_P1 (0x1) #define REG_PIH_ISR_P2 (0x2) #define REG_PIH_SIR (0x3) / BitField Definitions */ /* PIH_ISR_P1 Fields */ #define BIT_PIH_ISR_P1_PIH_ISR0 (0x000) #define BIT_PIH_ISR_P1_PIH_ISR0_M(0x0001) #define BIT_PIH_ISR_P1_PIH_ISR1 (0x001) #define BIT_PIH_ISR_P1_PIH_ISR1_M(0x0002) #define BIT_PIH_ISR_P1_PIH_ISR2 (0x002) #define BIT_PIH_ISR_P1_PIH_ISR2_M(0x0004) #define BIT_PIH_ISR_P1_PIH_ISR3 (0x003) #define BIT_PIH_ISR_P1_PIH_ISR3_M(0x0008) #define BIT_PIH_ISR_P1_PIH_ISR4 (0x004) #define BIT_PIH_ISR_P1_PIH_ISR4_M(0x0010) #define BIT_PIH_ISR_P1_PIH_ISR5 (0x005) #define BIT_PIH_ISR_P1_PIH_ISR5_M(0x0020) #define BIT_PIH_ISR_P1_PIH_ISR6 (0x006) #define BIT_PIH_ISR_P1_PIH_ISR6_M(0x0040) #define BIT_PIH_ISR_P1_PIH_ISR7 (0x007) #define BIT_PIH_ISR_P1_PIH_ISR7_M(0x0080) /* PIH_ISR_P2 Fields */ #define BIT_PIH_ISR_P2_PIH_ISR0 (0x000) #define BIT_PIH_ISR_P2_PIH_ISR0_M(0x0001) #define BIT_PIH_ISR_P2_PIH_ISR1 (0x001) #define BIT_PIH_ISR_P2_PIH_ISR1_M(0x0002) #define BIT_PIH_ISR_P2_PIH_ISR2 (0x002) #define BIT_PIH_ISR_P2_PIH_ISR2_M(0x0004) #define BIT_PIH_ISR_P2_PIH_ISR3 (0x003) #define BIT_PIH_ISR_P2_PIH_ISR3_M(0x0008) #define BIT_PIH_ISR_P2_PIH_ISR4 (0x004) #define BIT_PIH_ISR_P2_PIH_ISR4_M(0x0010) #define BIT_PIH_ISR_P2_PIH_ISR5 (0x005) #define BIT_PIH_ISR_P2_PIH_ISR5_M
Re: irqdesc porting help
Hi, My drivers in 2.6.14 use statements like desc->triggered = 1; And desc also points to some members of irqdesc which arent in 2.6.19 but in 2.6.14. Im a newbie, What changes am i supposed to make to make it work in 2.6.19. Im not sure what changes are exactly needed. Please Advice, Regards, Jo On 2/15/07, Russell King <[EMAIL PROTECTED]> wrote: On Thu, Feb 15, 2007 at 07:33:47PM +0900, Paul Mundt wrote: > On Thu, Feb 15, 2007 at 12:01:37PM +0530, Maximus wrote: > > Im trying to port some drivers between 2.6.14 and 2.6.19 > > > > I find that irqdesc has changed completely. how do i port > > the drivers between 2.6.14 and 2.6.19? > > > > is there a porting guide available to port the drivers > > which use irqdesc?. > > > > my drivers use variables triggered, ... which dont exist in 2.6.19 > > irqdesc strcuture. > > > Presumably you're talking about the struct hw_interrupt_type and the lack > of an irq_desc[irq].handler? There's some migration helper glue in > include/linux/irq.h that you can use, but you're better off converting > completely. You can at least get it building again by changing to > irq_desc[irq].chip, but you really want a proper irq_chip implementation > to go along with this, rather than munging in the hw_interrupt_type. It should be asked - why are drivers poking about in the irqdesc structure? -- Russell King Linux kernel2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: irqdesc porting help
Hi, My drivers in 2.6.14 use statements like desc-triggered = 1; And desc also points to some members of irqdesc which arent in 2.6.19 but in 2.6.14. Im a newbie, What changes am i supposed to make to make it work in 2.6.19. Im not sure what changes are exactly needed. Please Advice, Regards, Jo On 2/15/07, Russell King [EMAIL PROTECTED] wrote: On Thu, Feb 15, 2007 at 07:33:47PM +0900, Paul Mundt wrote: On Thu, Feb 15, 2007 at 12:01:37PM +0530, Maximus wrote: Im trying to port some drivers between 2.6.14 and 2.6.19 I find that irqdesc has changed completely. how do i port the drivers between 2.6.14 and 2.6.19? is there a porting guide available to port the drivers which use irqdesc?. my drivers use variables triggered, ... which dont exist in 2.6.19 irqdesc strcuture. Presumably you're talking about the struct hw_interrupt_type and the lack of an irq_desc[irq].handler? There's some migration helper glue in include/linux/irq.h that you can use, but you're better off converting completely. You can at least get it building again by changing to irq_desc[irq].chip, but you really want a proper irq_chip implementation to go along with this, rather than munging in the hw_interrupt_type. It should be asked - why are drivers poking about in the irqdesc structure? -- Russell King Linux kernel2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
irqdesc porting help
Im trying to port some drivers between 2.6.14 and 2.6.19 I find that irqdesc has changed completely. how do i port the drivers between 2.6.14 and 2.6.19? is there a porting guide available to port the drivers which use irqdesc?. my drivers use variables triggered, ... which dont exist in 2.6.19 irqdesc strcuture. Could anyone help me on this. Regards, Jo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
irqdesc porting help
Im trying to port some drivers between 2.6.14 and 2.6.19 I find that irqdesc has changed completely. how do i port the drivers between 2.6.14 and 2.6.19? is there a porting guide available to port the drivers which use irqdesc?. my drivers use variables triggered, ... which dont exist in 2.6.19 irqdesc strcuture. Could anyone help me on this. Regards, Jo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
