From: Valentine Barshak <vbarshak@ru.mvista.com>
To: Stefan Roese <sr@denx.de>
Cc: linuxppc-dev@ozlabs.org, Sean MacLennan <smaclennan@pikatech.com>
Subject: Re: Strange behavior with I2C on Sequoia board
Date: Thu, 21 Aug 2008 16:30:09 +0400 [thread overview]
Message-ID: <48AD5FD1.1090809@ru.mvista.com> (raw)
In-Reply-To: <200808211151.40499.sr@denx.de>
Stefan Roese wrote:
> On Thursday 21 August 2008, Sean MacLennan wrote:
>>> That's all output from the wrapper, not the kernel. And the kernel
>>> config doesn't make a difference at all to the wrapper. I wonder if
>>> there is some weird size issue going on there or if whatever U-Boot
>>> version you are using is doing odd things...
>> Any chance something in the DTS could affect it? Maybe try commenting
>> out the second IIC controller?
>
> Yes, I2C is generally working and should make a difference in Linux kernel
> booting.
>
> It seems that your bootwrapper is somehow not copying the correct MAC address
> to the device-tree. Not sure what's going wrong here. We usually don't use
> the bootwrapper but boot the uImage directly from U-Boot on all 4xx systems.
>
> You might want to debug the bootwrapper code, if possible drop the bootwrapper
> and use the uImage with a newer, device-tree enabled U-Boot version.
>
U-boot thinks that all memory above the first 8MB is out of reach for
the kernel and puts kernel bootargs and boardinfo structure below 8MB as
close as possible to this limit. Including the i2c driver into the
kernel increases the kernel image size. So when u-boot unpacks the
kernel to 0x400000 (Load Address: 00400000) it overwrites the kernel
parameters. So when the kernel actually starts, it reads zeros instead
of boardinfo (and mac addresses)
The 8MB limit is set for all AMCC boards in include/configs/amcc-common.h:
#define CFG_BOOTMAPSZ (8 << 20) /* Initial Memory map for Linux */
I think this limit is obsolete and can be moved to at least 64MB.
But you'll need to rebuild u-boot.
Stefan, what do you think? Can we increase the default initial memory
map for AMCC boards in the next u-boot release, since u-boot has all
memory identity-mapped on ppc 44x?
Thanks,
Valentine.
> Best regards,
> Stefan
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
next prev parent reply other threads:[~2008-08-21 12:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 20:55 Strange behavior with I2C on Sequoia board Steven A. Falco
2008-08-21 0:44 ` Josh Boyer
2008-08-21 3:18 ` Sean MacLennan
2008-08-21 9:51 ` Stefan Roese
2008-08-21 12:30 ` Valentine Barshak [this message]
2008-08-21 13:27 ` Steven A. Falco
2008-08-21 14:32 ` Stefan Roese
2008-08-21 14:33 ` Geert Uytterhoeven
2008-08-21 14:40 ` Stefan Roese
2008-08-21 18:45 ` Wolfgang Denk
2008-08-21 14:16 ` Stefan Roese
2008-08-21 18:45 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48AD5FD1.1090809@ru.mvista.com \
--to=vbarshak@ru.mvista.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=smaclennan@pikatech.com \
--cc=sr@denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.