[U-Boot-Users] About interrupt processing on MIPS32 4Kc
I am using Broadcom BCM7401 platform of MIPS32 4Kc bases.
This time, I decided to do u-boot porting.
In the midst of analyze source code, found out to u-boot's code for MIPS32 4Kc that interrupt processing part does not exist.
Why do not handle interrupt processing in u-boot of MIPS32 4Kc bases?
Could not find exception vector processing part.
relocate_code() exception vector thing which do relocation by memory be?
Basically, do not you use interrupt in u-boot of MIPS32 4Kc bases?
How do you treat devices(UART, Etherent,..) back differing without interrupt?
Are you doing polling?
I wonder very.
sai wrote:
I am using Broadcom BCM7401 platform of MIPS32 4Kc bases.
This time, I decided to do u-boot porting.
In the midst of analyze source code, found out to u-boot's code for MIPS32 4Kc that interrupt processing part does not exist.
Why do not handle interrupt processing in u-boot of MIPS32 4Kc bases?
Could not find exception vector processing part.
relocate_code() exception vector thing which do relocation by memory be?
Basically, do not you use interrupt in u-boot of MIPS32 4Kc bases?
How do you treat devices(UART, Etherent,..) back differing without interrupt?
Are you doing polling?
I wonder very.
Yongdae, Shin
U-boot runs polled mode rather than using interrupts (with a couple of exceptions). U-boot is single-threaded and simple (well, compared to linux). The rationale is that, if you want an interrupt driven multitasking system, run linux. ;-)
Best regards, gvb
participants (2)
-
Jerry Van Baren -
sai