From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Paul Mundt <lethal@linux-sh.org>,
Maximus <john.maximus@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: irqdesc porting help
Date: Thu, 15 Feb 2007 10:45:47 +0000 [thread overview]
Message-ID: <20070215104547.GA15772@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20070215103347.GA18690@linux-sh.org>
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:
next prev parent reply other threads:[~2007-02-15 10:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 6:31 Maximus
2007-02-15 10:33 ` Paul Mundt
2007-02-15 10:45 ` Russell King [this message]
2007-02-15 13:11 ` Maximus
2007-02-15 13:16 ` Russell King
2007-02-15 13:16 ` Arjan van de Ven
2007-02-20 7:03 ` Maximus
2007-02-20 10:54 ` Komal Shah
2007-02-20 10:58 ` Komal Shah
2007-02-20 11:48 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070215104547.GA15772@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=john.maximus@gmail.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®