From: Mikhail Zolotaryov <lebon@lebon.org.ua>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc 4xx: DDR0_14[REDUC] decoded incorrectly
Date: Mon, 09 Mar 2009 23:17:45 +0200 [thread overview]
Message-ID: <49B58779.9040905@lebon.org.ua> (raw)
In-Reply-To: <20090309171243.GA26415@zod.rchland.ibm.com>
>> However, "1" is decoded as 64 bit (8 byte), "0" - as 32 bit (4 byte) bus
>> by the kernel code. My understanding is this is not correct - patch
>> attached.
>
> You are missing the Signed-off-by tag that is needed.
>
I'm sorry.
Signed-off-by: Mikhail Zolotaryov <lebon@lebon.org.ua>
> Aside from that, I'm curious if you found this just through inspection, or
> if you actually had a problem because of it. Your fix seems correct, yet
> I've had no problems with my boards at all.
>
I'm actually working on custom PowerPC 440EPX board development here and
have found the problem: without applying changes described, Linux
detects memory size incorrectly and is unable to start. The rest of
memory size computation process seems to be correct.
I have checked Sequoia evaluation board with U-Boot 2009.1 and confirm
that original kernel code reported memory size correctly. So, for my
understanding, if computation algorithm was wrong but result was correct
- the problem is source data i.e. initial DDR configuration parameters
loaded by U-Boot (please don't give a damn that memory size is always
reported correctly by U-Boot - it's hard-coded constant there). I have
checked Sequoia board schematics (DES0211_11_SCH_11.pdf, page 5, unit
U1D) and noted that BankSel#1 is not connected, while bootloader memory
configuration is (board/amcc/sequoia/sdram.c):
mtsdram(DDR0_10, 0x00000300);
i.e. both Chip Selects used.
If I change this line to:
mtsdram(DDR0_10, 0x00000100);
memory is accessible, patched kernel detects memory size correctly and
kernel seems to be working well.
Please check my considerations, possibly it may be necessary to request
additional information from board manufacturer.
WARNING: multiple messages have this Message-ID (diff)
From: Mikhail Zolotaryov <lebon@lebon.org.ua>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc 4xx: DDR0_14[REDUC] decoded incorrectly
Date: Mon, 09 Mar 2009 23:17:45 +0200 [thread overview]
Message-ID: <49B58779.9040905@lebon.org.ua> (raw)
In-Reply-To: <20090309171243.GA26415@zod.rchland.ibm.com>
>> However, "1" is decoded as 64 bit (8 byte), "0" - as 32 bit (4 byte) bus
>> by the kernel code. My understanding is this is not correct - patch
>> attached.
>
> You are missing the Signed-off-by tag that is needed.
>
I'm sorry.
Signed-off-by: Mikhail Zolotaryov <lebon@lebon.org.ua>
> Aside from that, I'm curious if you found this just through inspection, or
> if you actually had a problem because of it. Your fix seems correct, yet
> I've had no problems with my boards at all.
>
I'm actually working on custom PowerPC 440EPX board development here and
have found the problem: without applying changes described, Linux
detects memory size incorrectly and is unable to start. The rest of
memory size computation process seems to be correct.
I have checked Sequoia evaluation board with U-Boot 2009.1 and confirm
that original kernel code reported memory size correctly. So, for my
understanding, if computation algorithm was wrong but result was correct
- the problem is source data i.e. initial DDR configuration parameters
loaded by U-Boot (please don't give a damn that memory size is always
reported correctly by U-Boot - it's hard-coded constant there). I have
checked Sequoia board schematics (DES0211_11_SCH_11.pdf, page 5, unit
U1D) and noted that BankSel#1 is not connected, while bootloader memory
configuration is (board/amcc/sequoia/sdram.c):
mtsdram(DDR0_10, 0x00000300);
i.e. both Chip Selects used.
If I change this line to:
mtsdram(DDR0_10, 0x00000100);
memory is accessible, patched kernel detects memory size correctly and
kernel seems to be working well.
Please check my considerations, possibly it may be necessary to request
additional information from board manufacturer.
next prev parent reply other threads:[~2009-03-09 21:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 16:21 [PATCH] powerpc 4xx: DDR0_14[REDUC] decoded incorrectly Mikhail Zolotaryov
2009-03-09 16:21 ` Mikhail Zolotaryov
2009-03-09 17:12 ` Josh Boyer
2009-03-09 17:12 ` Josh Boyer
2009-03-09 21:17 ` Mikhail Zolotaryov [this message]
2009-03-09 21:17 ` Mikhail Zolotaryov
2009-03-10 19:50 ` [PATCH] PowerPC 440EPx/GRx fix memory size calculation Valentine Barshak
2009-03-10 20:57 ` Mikhail Zolotaryov
2009-03-11 1:40 ` Valentine
2009-03-11 2:26 ` Benjamin Herrenschmidt
2009-03-11 8:24 ` Mikhail Zolotaryov
2009-03-11 8:29 ` Mikhail Zolotaryov
2009-03-11 10:37 ` Josh Boyer
2009-03-11 19:06 ` Valentine Barshak
2009-03-11 21:57 ` Josh Boyer
2009-03-11 22:08 ` Valentine
2009-03-11 23:07 ` Josh Boyer
2009-03-12 6:02 ` Stefan Roese
2009-03-12 7:32 ` Benjamin Herrenschmidt
2009-03-12 8:05 ` Stefan Roese
2009-03-12 8:12 ` Benjamin Herrenschmidt
2009-03-12 8:24 ` Stefan Roese
2009-03-12 8:45 ` Mikhail Zolotaryov
2009-03-12 10:45 ` Josh Boyer
2009-03-12 11:02 ` Stefan Roese
2009-03-13 23:01 ` Feng Kan
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=49B58779.9040905@lebon.org.ua \
--to=lebon@lebon.org.ua \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
/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.