David >-----Original Message----- >From: David Miller [mailto:da...@davemloft.net] >> dev_ifsioc_locked() >> case SIOCGIFMAP: >> ifr->ifr_map.irq = dev->irq; // ?? type mismatch >> >> Here >> ifr->ifr_map.irq) is of type unsigned char >> dev-irq is of type unsigned int >> >> So ifconfig reports a wrong irq number when the dev->irq number is > 255. > >This is a known and unavoidable limitation of this interface. >It's only real use is to control ISA style IRQs which are < 255.
On Zoom2 TI OMAP3 based board, the IRQ we are requesting is value=381 and hence the problem reported. We do understand that this would break all user level code. > >> I am confused to see the same typedefs in file: net/if.h >> Not sure how to make changes for the user side net/if.h file? Any idea why net/if.h user level file does not have same definitions as linux/if.h? In other words, what is the origin of net/if.h file? >> >> Signed-off-by: Moiz Sonasath <m-sonas...@ti.com> >> Signed-off-by: Vikram Pandita <vikram.pand...@ti.com> > >You can't make these kinds of changes, every userland binary out there >using this structure would break. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
