THe interrupt numbers are configured in the IVPRs( Interrupt Vector
Proiority Registers).
Those registers configure a particular interrupt ( sense,
level,enable,vector,priority)
The purpose of the vector is to map a physical register to a logical
interrupt "channel". Keep those settings, there are
, 2003 10:36 PM
To: linux-emb
Subject: Re: kernel boot on mpc8245, internal UART
> emanuel stiebler wrote:
>>I have a board which is close to Sandpoints mpc8245 cpu board.
>>(using internal DUARTs, EPIC_MODE_SERIAL)
Trying to figure out what is going wrong, I tried to locate the
Hi,
I was some experience for similar problem on past time. It was happened
on kernel porting process (to other board).
For my problem, It caused by ppc_md.calibrate_decr =
todc_calibrate_decr; . i forgot to initialize external real time clock(
so rtc was stopped). that means it does not work and
> emanuel stiebler wrote:
>>I have a board which is close to Sandpoints mpc8245 cpu board.
>>(using internal DUARTs, EPIC_MODE_SERIAL)
Trying to figure out what is going wrong, I tried to locate the driver
for the internal DUART of the MPC8245 ...
So, probably a stupid question, but where is the
Mark A. Greer wrote:
> My recommendation for a first step is to look at your printk data. You
> didn't miss a flag, you're simply crapping out before the console is set
> up to dump out the printk data.
>
> Go into the System.map file associated with the kernel your running,
> search for 'log_buf'
My recommendation for a first step is to look at your printk data. You
didn't miss a flag, you're simply crapping out before the console is set
up to dump out the printk data.
Go into the System.map file associated with the kernel your running,
search for 'log_buf', subtract 0xc000 to get the
Hi,
I have a board which is close to Sandpoints mpc8245 cpu board.
(using internal DUARTs, EPIC_MODE_SERIAL)
Trying to get it working, I got until:
Filename 'pImage'.
Load address: 0x100
Loading: T ###T
##
###T
###
