lkml.org 
[lkml]   [2007]   [Feb]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 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 <rmk+lkml@arm.linux.org.uk> 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 kernel 2.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 majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-02-15 14:13    [W:0.074 / U:0.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site