From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH] [RFC] Potential bug in defining 'irq field' of 'ifmap structure' Date: Tue, 07 Jul 2009 18:32:55 -0700 (PDT) Message-ID: <20090707.183255.193727664.davem@davemloft.net> References: <20090706.172501.136390568.davem@davemloft.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:43756 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755668AbZGHBcw (ORCPT ); Tue, 7 Jul 2009 21:32:52 -0400 In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: vikram.pandita@ti.com Cc: m-sonasath@ti.com, netdev@vger.kernel.org, linux-omap@vger.kernel.org From: "Pandita, Vikram" Date: Wed, 8 Jul 2009 02:27:51 +0530 > On Zoom2 TI OMAP3 based board, the IRQ we are requesting is > value=381 and hence the problem reported. The IRQ reported by this user call is only reliable for ISA devices. Or, ARM platforms could opt to use a virtual IRQ scheme like PowerPC and Sparc use, which keeps all device IRQs under 256.