| 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
| ||
|
Message-ID: <20080228172434.GA25737@ld0162-tx32.am.freescale.net> Date: Thu, 28 Feb 2008 11:24:34 -0600 From: Scott Wood <scottwood@...escale.com> To: biswa.nayak@...ro.com Cc: linuxppc-dev@...abs.org, linux-kernel@...r.kernel.org Subject: Re: Wrong IRQ assigned on MPC8349EMDS board On Thu, Feb 28, 2008 at 09:38:36PM +0530, biswa.nayak@...ro.com wrote: > I found that the IRQ lines assigned to different peripherals are > completely wrong. > My serial ports are connected to pin 9 and 10, but in this kernel the > IRQs assigned are 16 and 17. These are virtual IRQ numbers, which have nothing to do with the IPIC IRQ numbers. > On a little investigation I found that the base address assigned to the > IPIC chip is '0xFDDFB700' That's a virtual address returned from ioremap(), not the physical address of the IPIC. > Does this wrong assignment is due to the wrong base address of the IPIC > chip? > With IRQs 16 and 17, how the serial console is working fine? > > When I tried hard coding the IPIC base value to '0xfe000700' then the > system refuses to boot up. That might be a hint that things aren't as wrong as you think. :-) > I kept the IPIC base as 0xfddfb700 and hard coded the irq lines for > serial ports as 9 and 10 > and in that case the 'request_irq' call fails with the error number as > '-38', > which translates to '-ENOSYS'. Likewise. -Scott -- 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