Le 22/01/2011 08:21, Reinhard Meyer a écrit :
>> But this leads me to the question what happens with the stuff in the
>> data section. Seems I should have again a look at the lowlevel stuff to
>> understand that.
>
> Intuitively (without looking at the code) I would think that
> CONST DATA is ok,
Dear Alexander Holler,
> Am 22.01.2011 07:38, schrieb John Rigby:
>> On Fri, Jan 21, 2011 at 11:07 PM, Alexander Holler
>> wrote:
>>> Hello,
>>>
>>> because I still have problems where I think the problem is the
>>> relocation, I've had a look at some timer code.
>>>
>>> E.g. in arch/arm/cpu/ar
Am 22.01.2011 07:38, schrieb John Rigby:
> On Fri, Jan 21, 2011 at 11:07 PM, Alexander Holler
> wrote:
>> Hello,
>>
>> because I still have problems where I think the problem is the
>> relocation, I've had a look at some timer code.
>>
>> E.g. in arch/arm/cpu/arm926ejs/kirkwood/timer.c on top th
On Fri, Jan 21, 2011 at 11:07 PM, Alexander Holler wrote:
> Hello,
>
> because I still have problems where I think the problem is the
> relocation, I've had a look at some timer code.
>
> E.g. in arch/arm/cpu/arm926ejs/kirkwood/timer.c on top there is
>
> struct kwtmr_registers *kwtmr_regs = (str
Hello,
because I still have problems where I think the problem is the
relocation, I've had a look at some timer code.
E.g. in arch/arm/cpu/arm926ejs/kirkwood/timer.c on top there is
struct kwtmr_registers *kwtmr_regs = (struct kwtmr_registers
*)KW_TIMER_BASE;
which is used in timer_init().
5 matches
Mail list logo