From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] Mvbge driver broken on kirkwood platforms after ARM relocation
Date: Wed, 06 Oct 2010 17:56:07 +0200 [thread overview]
Message-ID: <4CAC9C17.2000206@free.fr> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D19A69E25E2@SC-VEXCH4.marvell.com>
Le 06/10/2010 16:22, Prafulla Wadaskar a ?crit :
>
>
>> -----Original Message-----
>> From: Wolfgang Denk [mailto:wd at denx.de]
>> Sent: Wednesday, October 06, 2010 7:00 PM
>> To: Prafulla Wadaskar
>> Cc: Albert ARIBAUD; u-boot at lists.denx.de; Ashish Karkare;
>> Prabhanjan Sarnaik
>> Subject: Re: [U-Boot] Mvbge driver broken on kirkwood
>> platforms after ARM relocation
>>
>> Dear Prafulla Wadaskar,
>>
>> In message
>> <F766E4F80769BD478052FB6533FA745D19A69E25C8@SC-VEXCH4.marvell.
>> com> you wrote:
>>>
>>> After rebasing to new ARM relocation code base and updating
>> Kirkwood board support.
>>> I am unable to get my network driver through (mvgbe)
>>>
>>> Have you tested this on edminv2 platform?
>>> If it is working at your end? Can you please cross check
>> the same with Kirkwood platform?
>>
>> Try running the "dcache off" command before accessing the network and
>> see if this changes anything.
>
> I tried this too, I have disabled dcache in init.
> .. no difference.
>
> Debugging continued..
>
> Regards..
> Prafulla . .
Trying this on an openrd client board with the openrd_base config. Both
boards have the same exact RAMs, however the DRAM: line is acting funny
on me: fresh with my relocation patch above master, it says:
SoC: Kirkwood 88F6281_A0
DRAM: 192.5 MiB
... while the actual RAM size is 512 MiB.
(Even considering that the original Marvell code may have the
count-only-half bug that Chris' patch fixes, that's only 385 MiB...
Weirder yet: adding Chris' patch above mine, I get 3.6 GiB... But let's
chase only one rabbit at a time)
Prafulla, how much RAM does your build see on your board(s)?
Amicalement,
--
Albert.
next prev parent reply other threads:[~2010-10-06 15:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 22:22 [U-Boot] [PATCH] orion5x: optimize window size computation Albert Aribaud
2010-10-05 5:57 ` Prafulla Wadaskar
2010-10-05 21:40 ` Chris Moore
2010-10-06 5:51 ` Albert ARIBAUD
2010-10-06 9:34 ` Prafulla Wadaskar
2010-10-06 13:29 ` Wolfgang Denk
2010-10-06 13:47 ` Albert ARIBAUD
2010-10-06 14:24 ` Prafulla Wadaskar
2010-10-06 9:38 ` [U-Boot] Mvbge driver broken on kirkwood platforms after ARM relocation Prafulla Wadaskar
2010-10-06 13:30 ` Wolfgang Denk
2010-10-06 13:54 ` Albert ARIBAUD
2010-10-06 13:56 ` Albert ARIBAUD
2010-10-06 14:14 ` Prafulla Wadaskar
2010-10-06 14:43 ` Albert ARIBAUD
2010-10-06 14:22 ` Prafulla Wadaskar
2010-10-06 15:56 ` Albert ARIBAUD [this message]
2010-10-06 17:36 ` Albert ARIBAUD
2010-10-06 17:54 ` Albert ARIBAUD
2010-10-07 4:37 ` Prafulla Wadaskar
2010-10-07 9:57 ` Prafulla Wadaskar
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=4CAC9C17.2000206@free.fr \
--to=albert.aribaud@free.fr \
--cc=u-boot@lists.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.