CONFIG_MTD_PHYSMAP_START

CONFIG_MTD_PHYSMAP_START

[Alex]

Also (in addition to my previous post, where I am questioning the correctness of the output, stating that address belongs to RAM while it clearly does not !), Thomas wrote:

>> The initial boot provides the following:
>> Memory map:
>> /* Chip Select FLASH Normal */
>> #define BR0_VAL 0x04000801 /* Offset=0x04000000 PS=16 GPCM Valid=1 */
>> #define OR0_VAL     0xFFC00160  /* OK */

>The value you are using is the value, which is programmed into the BR0
>register of the CPU. 
>BRx = Bank Register for chipselect x
>ORx = Option Register for chipselect x
>The values in those registers define the start address, buswitdh, size,
>timings for the chipselects. So using those values is definitely not a
>good idea. Of course you can decode the values in the registers to get
>your real address values. 

- it looks that I am in the "chicken" and the "egg" problem ...
According to Thomas (see above), I can not rely on the flash phys start address, given to me "verbotum" - so I can not set the value in .config 
for CONFIG_MTD_PHYSMAP_START ... 
Thomas - in what software you advise me to "decode the values in the registers to get real address values" ? 

Thanks,
Best Regards,
Alex


___________________________________________________________________
Speed up your surfing with Juno SpeedBand.
Now includes pop-up blocker!
Only $14.95/month -visit http://www.juno.com/surf to sign up today!

CONFIG_MTD_PHYSMAP_START

[Alex]

As a reference I am supplying relevant
 content of my .config file 
- could someone please pinpoint to me
 what options need to be changed 
or invoked to correct my current problem
(driver interprets 0x04000000 as RAM address for 32Mb DRAM,
with highest address being 0x02000000).

Thanks,
***************************
...
#
# Memory Technology Devices (MTD)
#
CONFIG_MTD=y
CONFIG_MTD_DEBUG=y
CONFIG_MTD_DEBUG_VERBOSE=3
CONFIG_MTD_PARTITIONS=y
# CONFIG_MTD_CONCAT is not set
# CONFIG_MTD_REDBOOT_PARTS is not set
CONFIG_MTD_CMDLINE_PARTS=y

#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLOCK=y
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set

#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=y
# CONFIG_MTD_JEDECPROBE is not set
CONFIG_MTD_GEN_PROBE=y
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
# CONFIG_MTD_CFI_INTELEXT is not set
CONFIG_MTD_CFI_AMDSTD=y
CONFIG_MTD_CFI_AMDSTD_RETRY=0
# CONFIG_MTD_CFI_STAA is not set
CONFIG_MTD_CFI_UTIL=y
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
# CONFIG_MTD_OBSOLETE_CHIPS is not set

#
# Mapping drivers for chip access
#
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
CONFIG_MTD_PHYSMAP=y
CONFIG_MTD_PHYSMAP_START=0x04000801
CONFIG_MTD_PHYSMAP_LEN=0x400000
CONFIG_MTD_PHYSMAP_BANKWIDTH=2
# CONFIG_MTD_RPXLITE is not set
# CONFIG_MTD_CFI_FLAGADM is not set

#
# Self-contained MTD device drivers
#
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLKMTD is not set

#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOC2001PLUS is not set

#
# NAND Flash Device Drivers
#
CONFIG_MTD_NAND=y
# CONFIG_MTD_NAND_VERIFY_WRITE is not set
CONFIG_MTD_NAND_IDS=y
# CONFIG_MTD_NAND_DISKONCHIP is not set
                                                              

___________________________________________________________________
Speed up your surfing with Juno SpeedBand.
Now includes pop-up blocker!
Only $14.95/month -visit http://www.juno.com/surf to sign up today!

Re: CONFIG_MTD_PHYSMAP_START

[Thomas Gleixner]

Yor mail client still sends lines > 80 chars 

On Wed, 2005-02-02 at 19:49 +0000, Alex wrote:
> Also (in addition to my previous post, where 
> I am questioning the correctness of the output, 
> stating that address belongs to RAM while it clearly does not !), 

Would you consider to read TFA ?
>> 2. It's inside the reserved physical address space of RAM

> - it looks that I am in the "chicken" and the "egg" problem ...
> According to Thomas (see above), I can not rely on the 
> flash phys start address, given to me "verbotum" - 

Given "verbotum" - I guess you meant verbatim. Some one told you to use
0x000801, which is definitely wrong. Can you please provide the verbatim
information which was given to you ?

You could also point to some valuable information about the board
(vendor, user manual ....)

> so I can not set the value in .config 
> for CONFIG_MTD_PHYSMAP_START ... 
> Thomas - in what software you advise me to "decode the 
> values in the registers to get real address values" ? 

Again: RTFA
>> I have no datasheet handy, but you should definitely read it :)

The registers are described there. Do you expect that I download the
datasheet and decode this for your conveniance ? I can do so, please
contact me offlist and talk to your manager about a support contract.

tglx

Re: CONFIG_MTD_PHYSMAP_START

[Thomas Gleixner]

Keep your postings in the Mail thread by hitting the reply button.

On Wed, 2005-02-02 at 21:49 +0000, Alex wrote:
> As a reference I am supplying relevant

You meant irrelevant.

> CONFIG_MTD_PHYSMAP_START=0x04000801

As explained already, this address is definitely wrong.

Provide relevant information. We are not good in witchcraft and wizardy.

tglx

Re: CONFIG_MTD_PHYSMAP_START

[David Woodhouse]

On Wed, 2005-02-02 at 23:14 +0100, Thomas Gleixner wrote:
> Keep your postings in the Mail thread by hitting the reply button.

His reply button is broken; his mailer doesn't conform to RFC2822.

Alex, please use a non-broken mailer if you want to use this forum.
Omitting 'Re:' from the subject to get round the automatic filtering
isn't acceptable either. All traffic from you will be trapped for
moderation until I'm sure you are behaving correctly.

The address 0x04000801 is definitely not correct for the physical
address of the start of flash. Consult your board documentation or
schematics and find the correct value.

-- 
dwmw2