From: Valentine Barshak <vbarshak@ru•mvista.com>
To: Imre Kaloz <kaloz@openwrt•org>
Cc: linuxppc-dev@ozlabs•org, Stefan Roese <sr@denx•de>
Subject: Re: [PATCH] MTD support for the AMCC Taishan
Date: Thu, 07 Feb 2008 17:55:14 +0300 [thread overview]
Message-ID: <47AB1BD2.9070104@ru.mvista.com> (raw)
In-Reply-To: <op.t55r5tt22s3iss@ecaz.afh.b-m.hu>
Imre Kaloz wrote:
> On Thu, 07 Feb 2008 15:05:23 +0100, Valentine Barshak
> <vbarshak@ru•mvista.com> wrote:
>
>>> Well, arch/ppc calculates the mtd2 dynamically and doesn't create
>>> a separate partition for kozio.
>>
>> That dynamic size calculation depends on the flash size.
>> The board I use has a 64MB NOR flash (I'm not aware of other Taishan
>> boards having chips of different size). So AFAIU if such board exists,
>> we'll need a cuboot flash-size fixup.
>
>
> All Taishan boards have 64MB flash (2x32MB). Denx was doing the size
> calculation
> to dynamically allocate mtd2 based on the size of mtd0+mtd1 if I recall
> right.
>
This is actually the code:
arch/ppc/platforms/4xx/taishan.c:static int taishan_setup_flash(void)
{
taishan_nor_parts[2].size = __res.bi_flashsize -
RW_PART0_SZ - RW_PART1_SZ - RW_PART3_SZ - RW_PART4_SZ;
Thanks,
Valentine.
>
> Cheers,
> Imre
next prev parent reply other threads:[~2008-02-07 14:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 10:41 [PATCH] MTD support for the AMCC Taishan Imre Kaloz
2008-02-07 10:29 ` Imre Kaloz
2008-02-07 12:00 ` Josh Boyer
2008-02-07 13:46 ` Valentine Barshak
2008-02-07 13:54 ` Imre Kaloz
2008-02-07 14:05 ` Valentine Barshak
2008-02-07 14:35 ` Imre Kaloz
2008-02-07 14:55 ` Valentine Barshak [this message]
2008-02-08 14:27 ` Stefan Roese
2008-02-08 14:32 ` Stefan Roese
2008-03-17 13:48 ` [PATCH v2] " Imre Kaloz
2008-03-17 14:27 ` Imre Kaloz
2008-06-05 12:50 ` Imre Kaloz
2008-06-05 13:15 ` Josh Boyer
2008-06-06 14:16 ` Stefan Roese
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=47AB1BD2.9070104@ru.mvista.com \
--to=vbarshak@ru$(echo .)mvista.com \
--cc=kaloz@openwrt$(echo .)org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=sr@denx$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox