[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.02.1302272243340.22263@ionos>
Date: Wed, 27 Feb 2013 23:00:36 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Russell King - ARM Linux <linux@....linux.org.uk>
cc: Santosh Shilimkar <santosh.shilimkar@...com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
john.stultz@...aro.org, viresh.kumar@...aro.org,
jacob.jun.pan@...ux.intel.com,
linux-arm-kernel@...ts.infradead.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, linaro-kernel@...ts.linaro.org,
patches@...aro.org, linus.walleij@...ricsson.com
Subject: Re: [PATCH 0/4] time: dynamic irq affinity
On Wed, 27 Feb 2013, Russell King - ARM Linux wrote:
> On Wed, Feb 27, 2013 at 11:30:11AM +0530, Santosh Shilimkar wrote:
> > P.S: Time and again it proves that making the local timer wakeup
> > capable solves the issue.
>
> Slightly different take: it proves that hardware people don't talk to
> software people about what they require to make an operating system
> work. Hardware people think they understand that and go off and do
> their own thing, and expect software people to sort out their mess.
>
> This happens all the time; there is no solution for it as long as
> companies view the creation of hardware as being entirely separate
> from software.
Amen!
We have seen the mess this kind of thinking creates on x86 already 10+
years ago and we are still suffering.
As I said before, I really can't understand that ARM and the ARM SoC
vendors insisted to repeat the same mistakes, which we kernel people
have proven to be fatal already. It's even worse: they asked me what
problems they should avoid before they went to implement them.
I can halfways understand the little kid who insists to burn his hand
on the hot oven instead of listening to parental advice, but this kind
of advisory resistance is either caused by abuse of secrect drugs or
by living in a disconnected universe or both.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists