* Oops accessing BCSR on 8272ADS
@ 2005-10-07 15:37 Alex Zeffertt
2005-10-07 15:47 ` Vitaly Bordug
0 siblings, 1 reply; 3+ messages in thread
From: Alex Zeffertt @ 2005-10-07 15:37 UTC (permalink / raw)
To: linuxppc-embedded
Hi list,
I've just downloaded linux-2.4.31 from kernel.org and compiled it for
the mpc8272ads board.
When I boot the kernel it oopses in fcc_enet.c:init_fcc_startup() at
the point where it tries to write to the BCSR.
Does anybody know why writing to the BCSR should cause a machine
check?
TIA,
Alex
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Oops accessing BCSR on 8272ADS
2005-10-07 15:37 Oops accessing BCSR on 8272ADS Alex Zeffertt
@ 2005-10-07 15:47 ` Vitaly Bordug
[not found] ` <20051007165749.305c6bd3.ajz@cambridgebroadband.com>
0 siblings, 1 reply; 3+ messages in thread
From: Vitaly Bordug @ 2005-10-07 15:47 UTC (permalink / raw)
To: Alex Zeffertt; +Cc: linuxppc-embedded list
Alex Zeffertt wrote:
> Hi list,
>
> I've just downloaded linux-2.4.31 from kernel.org and compiled it for
> the mpc8272ads board.
>
> When I boot the kernel it oopses in fcc_enet.c:init_fcc_startup() at
> the point where it tries to write to the BCSR.
>
> Does anybody know why writing to the BCSR should cause a machine
> check?
>
I guess I was not ioremapped/io_block_mapped properly.
Take a look into arch/ppc/kernel/m8260_setup.c m8260_map_io() function.
Anyway BCSR is better to be ioremapped in the place it is required.
> TIA,
>
> Alex
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
--
Sincerely,
Vitaly
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Oops accessing BCSR on 8272ADS
[not found] ` <43469CCD.5010404@ru.mvista.com>
@ 2005-10-07 16:19 ` Alex Zeffertt
0 siblings, 0 replies; 3+ messages in thread
From: Alex Zeffertt @ 2005-10-07 16:19 UTC (permalink / raw)
To: Vitaly Bordug, linuxppc-embedded
> >
> It depends on which u-boot you're using and there I'm aware of
> issues when BCSR resides somewhere different... Try 0xF8000000.
> Don't you have btw
>
Thanks Vitaly. You were right. In my u-boot - version 1.1.1 - it was
0xf8000000 not 0xf4500000. I just modified BCSR_ADDR and that stopped
the oops.
Cheers,
Alex
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-10-07 16:19 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-10-07 15:37 Oops accessing BCSR on 8272ADS Alex Zeffertt
2005-10-07 15:47 ` Vitaly Bordug
[not found] ` <20051007165749.305c6bd3.ajz@cambridgebroadband.com>
[not found] ` <43469CCD.5010404@ru.mvista.com>
2005-10-07 16:19 ` Alex Zeffertt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).