linux-kernel - Re: irqdesc porting help

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 20 Feb 2007 12:33:18 +0530
From:	Maximus <john.maximus@...il.com>
To:	"Paul Mundt" <lethal@...ux-sh.org>, linux-kernel@...r.kernel.org,
	arjan@...radead.org
Subject: 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 <lethal@...ux-sh.org> 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.
>

View attachment "twl4030_core.c" of type "text/x-csrc" (36609 bytes)