From: Ingo Molnar <mingo@elte.hu>
To: David Miller <davem@davemloft.net>
Cc: sam@ravnborg.org, kosaki.motohiro@jp.fujitsu.com,
yinghai@kernel.org, linux-kernel@vger.kernel.org,
sparclinux@vger.kernel.org, tglx@linutronix.de
Subject: Re: irqnr fallout in gpiolib on sparc32
Date: Tue, 06 Jan 2009 12:57:04 +0000 [thread overview]
Message-ID: <20090106125704.GC20407@elte.hu> (raw)
In-Reply-To: <20090105.123734.137888898.davem@davemloft.net>
* David Miller <davem@davemloft.net> wrote:
> From: Ingo Molnar <mingo@elte.hu>
> Date: Mon, 5 Jan 2009 14:55:08 +0100
>
> > * Sam Ravnborg <sam@ravnborg.org> wrote:
> >
> > > Dave has mentioned this but we are not working actively on it yet.
> >
> > would be cool to do it - i think sparc32 is one of the last major
> > physical architectures to not be on genirq -
>
> m68k remains to be converted over to genirq as well
yeah - but m68k has been a holdout from pretty much every optional core
kernel facility that has been introduced in the past 5-10 years. So if
sparc32 converts to genirq we have a stronger case for saying:
"Convert, else ..."
[ where the three dots stands for something not nice. ]
Sparc32 on the other hand had a clean IRQ layer long before x86 found its
desire for a clean genirq layer - so genirq is a nuisance for Sparc32 at
best and it deserves none of the not nice actions. What i am hoping for is
that perhaps the Sparc unification changed that equation.
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: David Miller <davem@davemloft.net>
Cc: sam@ravnborg.org, kosaki.motohiro@jp.fujitsu.com,
yinghai@kernel.org, linux-kernel@vger.kernel.org,
sparclinux@vger.kernel.org, tglx@linutronix.de
Subject: Re: irqnr fallout in gpiolib on sparc32
Date: Tue, 6 Jan 2009 13:57:04 +0100 [thread overview]
Message-ID: <20090106125704.GC20407@elte.hu> (raw)
In-Reply-To: <20090105.123734.137888898.davem@davemloft.net>
* David Miller <davem@davemloft.net> wrote:
> From: Ingo Molnar <mingo@elte.hu>
> Date: Mon, 5 Jan 2009 14:55:08 +0100
>
> > * Sam Ravnborg <sam@ravnborg.org> wrote:
> >
> > > Dave has mentioned this but we are not working actively on it yet.
> >
> > would be cool to do it - i think sparc32 is one of the last major
> > physical architectures to not be on genirq -
>
> m68k remains to be converted over to genirq as well
yeah - but m68k has been a holdout from pretty much every optional core
kernel facility that has been introduced in the past 5-10 years. So if
sparc32 converts to genirq we have a stronger case for saying:
"Convert, else ..."
[ where the three dots stands for something not nice. ]
Sparc32 on the other hand had a clean IRQ layer long before x86 found its
desire for a clean genirq layer - so genirq is a nuisance for Sparc32 at
best and it deserves none of the not nice actions. What i am hoping for is
that perhaps the Sparc unification changed that equation.
Ingo
next prev parent reply other threads:[~2009-01-06 12:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 13:29 irqnr fallout in gpiolib on sparc32 Sam Ravnborg
2009-01-05 13:29 ` Sam Ravnborg
2009-01-05 13:38 ` Ingo Molnar
2009-01-05 13:38 ` Ingo Molnar
2009-01-05 13:48 ` Sam Ravnborg
2009-01-05 13:48 ` Sam Ravnborg
2009-01-05 13:55 ` Ingo Molnar
2009-01-05 13:55 ` Ingo Molnar
2009-01-05 20:37 ` David Miller
2009-01-05 20:37 ` David Miller
2009-01-06 12:57 ` Ingo Molnar [this message]
2009-01-06 12:57 ` Ingo Molnar
2009-01-06 16:29 ` David Miller
2009-01-06 16:29 ` David Miller
2009-01-07 13:02 ` Ingo Molnar
2009-01-07 13:02 ` Ingo Molnar
2009-01-07 13:34 ` Sam Ravnborg
2009-01-07 13:34 ` Sam Ravnborg
2009-01-07 21:08 ` David Miller
2009-01-07 21:08 ` David Miller
2009-01-06 23:43 ` KOSAKI Motohiro
2009-01-06 23:43 ` KOSAKI Motohiro
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=20090106125704.GC20407@elte.hu \
--to=mingo@elte.hu \
--cc=davem@davemloft.net \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yinghai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.