installing vector table

> Hi,
> I may not be answering all ur questions, but i can answer ur question
> regarding IVT relocation to SDRAM or SRAM. You can reloacte the vector table
> to SDRAM or SRAM. To achieve this you should create an appropriate mmu
> entry. For example, if CR_V bit says that the vector is at low address
> (0x0000000)
> and if you want to place the IVT at an SDRAM address say, 'X' then create an
> mmu entry to map the virtual address 0 to physical address X. Now, when
> there is an interrupt the processor generates 0x18 address which will go
> thru mmu and get translated to phy addr 'X' + 0x18.
>
> Hope this helps.
>
> Regards,
> Shankar
>
>
> >From: "Martin Siu"
> >To:
> >Subject: installing vector table
> >Date: Fri, 21 May 2004 18:42:33 +0800
> >
> >Dear ARM linux developers,
> >
> >There are some basic concepts in ARM linux that I didn't quite understand.
> >Could you please give me some pointers to
> >information?
> >
> > >From my studies on the generic ARM kernel source, the vector table is
> >usually installed at boot time to an address
> >defined in vectors_base(). This vector address is located either at
> >0xFFFF0000 or 0x00000000, determined by the CR_V
> >(bit 13) of the cr_alignment variable. When the vector address is set at
> >0xFFFF0000, we are basically relocating the
> >vectors from 0x0 to a high address.
> >
> >Here are my questions:
> >1) Does most (or all) ARM core proccessor support this vector relocation
> >feature?
> >2) I have an ARM7TDMI platform with a ROM at 0x0. I have customized my 2.4
> >kernel with some other XIP configs such that
> >the vector table is compiled and burned onto 0x0 prior to kernel bootup. I
> >have also added some compile options
> >(#define's) such that the vector installation (trap_init) is skipped at
> >runtime. My config actually works out and I have
> >a live kernel running this way. I was wondering whether my ARM7TDMI can
> >relocate the vector to some other write-able
> >addresses (eg, SRAM, SDRAM)?? It seems that my vector config is an
> >overkill.
> >If so, where and how should I set the CR_V bit of the cr_alignment? I've
> >greped my way through the kernel source but
> >have little clues.
> >
> >regards,
> >Martin
> >