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:	Thu, 09 Oct 2008 10:05:03 +0300
From:	Paulius Zaleckas <paulius.zaleckas@...tonika.lt>
To:	David Miller <davem@...emloft.net>
CC:	netdev@...r.kernel.org
Subject: Re: [PATCH] phy_device: Interrupt number 0 is valid

David Miller wrote:
> From: Paulius Zaleckas <paulius.zaleckas@...tonika.lt>
> Date: Wed, 08 Oct 2008 15:16:32 +0300
> 
>> If interrupt number 0(valid interrupt number) will be passed as
>> phy interrupt it should be used. In current situation even phy
>> polling will not work since PHY_POLL = -1
>>
>> Signed-off-by: Paulius Zaleckas <paulius.zaleckas@...tonika.lt>
> 
> In the Linux kernel, interrupt number 0 is defined as not valid.

Where it is defined as not valid?
Maybe it is not valid under x86, but it is valid at least on
ARM for sure.
Anyway if interrupt 0 is not valid then request_irq() will fail
and PHY_POLL will be used.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ