linux-kernel - Re: [RFC PATCH v3] irqchip: Add support for Tango interrupt controller

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]

Message-ID: <56A25CA3.9000001@sigmadesigns.com>
Date:	Fri, 22 Jan 2016 17:45:23 +0100
From:	Marc Gonzalez <marc_gonzalez@...madesigns.com>
To:	Mans Rullgard <mans@...sr.com>
CC:	Marc Zyngier <marc.zyngier@....com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Jason Cooper <jason@...edaemon.net>,
	LKML <linux-kernel@...r.kernel.org>,
	Linux ARM <linux-arm-kernel@...ts.infradead.org>,
	Sebastian Frias <sf84@...oste.net>
Subject: Re: [RFC PATCH v3] irqchip: Add support for Tango interrupt
 controller

On 22/01/2016 17:39, Måns Rullgård wrote:

> Marc Gonzalez <marc_gonzalez@...madesigns.com> writes:
> 
>> On 22/01/2016 17:35, Måns Rullgård wrote:
>>
>>> Marc Gonzalez <marc_gonzalez@...madesigns.com> writes:
>>>
>>>> With your latest patch, can I drop the ranges property?
>>>
>>> Why would you want to do that?
>>
>> <confused> I thought that was the whole point of the v4 improvement?
> 
> The point was to make it work right *if* someone were to do that even
> though having it there better reflects what the hardware actually looks
> like.

That's the part I'm struggling to understand. Who other than you or me
would write a device tree from scratch for this interrupt controller?