On Tuesday 14 July 2009 14:31:50 Eibach, Dirk wrote:
> > > Hmm, not sure yet what causes the problem here, but this changes in
> > > cpu/ppc4xx/start.S look fishy...
>
> I found that the old code does not clear TLB entry #0.
> So this helps in my case:
Yes, I already generated exactly this patch h
> > Hmm, not sure yet what causes the problem here, but this changes in
> > cpu/ppc4xx/start.S look fishy...
I found that the old code does not clear TLB entry #0.
So this helps in my case:
diff --git a/cpu/ppc4xx/start.S b/cpu/ppc4xx/start.S
index ac96fc2..7be73a7 100644
--- a/cpu/ppc4xx/sta
On Tuesday 14 July 2009 11:19:16 Eibach, Dirk wrote:
> > Otherwise "git bisect" is your fried...
>
> "git bisect" rocks!
:)
> So I finally found the nasty bugger:
>
> commit d873133f2ba9bd613d5f6552c31cc70fb13f15d3
> Author: Stefan Roese
> Date: Mon May 11 13:46:14 2009 +0200
>
> ppc4xx: A
> Otherwise "git bisect" is your fried...
"git bisect" rocks!
So I finally found the nasty bugger:
commit d873133f2ba9bd613d5f6552c31cc70fb13f15d3
Author: Stefan Roese
Date: Mon May 11 13:46:14 2009 +0200
ppc4xx: Add Sequoia RAM-booting target
Hmm, not sure yet what causes the problem he
On Monday 13 July 2009 16:28:33 Eibach, Dirk wrote:
> > > I narrowed it down to board_early_init_r() where
> >
> > remove_tlb() is done.
> >
> > Before or after the remove_tlb()?
>
> It is in remove_tlb().
OK.
> > > When I do a 'res halt' 'res run' sequence with the BDI the
> >
> > board comes
>
> > I narrowed it down to board_early_init_r() where
> remove_tlb() is done.
>
> Before or after the remove_tlb()?
It is in remove_tlb().
> > When I do a 'res halt' 'res run' sequence with the BDI the
> board comes
> > up fine.
> >
> > Any ideas?
>
> No, sorry. I haven't done much work on C
Hi Dirk,
On Monday 13 July 2009 16:07:30 Eibach, Dirk wrote:
> > Perhaps it would be doable to extract the board specific
> > stuff into some board file and use common code for the real
> > command and I2C-EEPROM handling. We could move these
> >
> > declarations into the board specific file:
> >
> > The bootstrap.c file is the same as for Canyonlands. Maybe it makes
> > sense to share it between all 460EX boards, by moving it to some
> > common location. Stefan, what do you think ?
>
> I'm not so sure here. Even if those settings might work on
> most 460EX/GT boards, some custom boar
On Monday 13 July 2009 15:45:05 Felix Radensky wrote:
> The bootstrap.c file is the same as for Canyonlands. Maybe it makes
> sense to share it between all 460EX boards, by moving it to some
> common location. Stefan, what do you think ?
I'm not so sure here. Even if those settings might work on m
Hi, Dirk
The bootstrap.c file is the same as for Canyonlands. Maybe it makes
sense to share it between all 460EX boards, by moving it to some
common location. Stefan, what do you think ?
Felix.
Dirk Eibach wrote:
> Board support for the Guntermann & Drunck CompactCenter and
> DevCon-Center.
> Ba
Dirk,
On Monday 13 July 2009 11:28:22 Dirk Eibach wrote:
> Board support for the Guntermann & Drunck CompactCenter and
> DevCon-Center.
> Based on the AMCC Canyonlands board support by Stefan Roese.
>
> Signed-off-by: Dirk Eibach
> ---
> Changes since v1:
> - removed dead code
> - whitespace clea
Board support for the Guntermann & Drunck CompactCenter and
DevCon-Center.
Based on the AMCC Canyonlands board support by Stefan Roese.
Signed-off-by: Dirk Eibach
---
Changes since v1:
- removed dead code
- whitespace cleanup
- simplified code for nand/nor distinction in
board/gdsys/compactcente
12 matches
Mail list logo
