[ELDK] Ramdisk image for 2.6.34 linux

[Wolfgang Denk]

Dear Alex,

In message <E1OYeYJ-0000Li-00.alex_daniloff-mail-ru at f29.mail.ru> you wrote:
>
> > > > Whoy whoud you want to do that? A ramdisk of that size is the worst
> > > > choice of a root file system you can make. Please read the manual!
> > 
> > You seem to ignore my hints...
> 
> No

Hm... Then would you please be so kind and elucidate why you build a
32 MB big ramdisk, knowing about the inherent problems and
disadvantages?

> > > > > Kernel command line: ramdisk_size=32768 root=/dev/ram rw console=ttyS2,115200
> > > > -----------------------------------------------------------^^^^^^^^^^^^^
> > > > 
> > > > Are you sure of this?
> > > > 
> > > > Is this really supported in your kernel port, and in your device tree?
> > 
> > and again...
> 
> this is correct console port for my board, in default case (ttyS0) i will lose console output after removing early console 

That was not my question.

My questions were:

- Is this really supported in your kernel port?

- Is this really supported in your device tree?


> which ramdisk variables i have to add to enviroments and bootargs?

Again, this was not my question.

You quoted:

> > => bootm 400000
> > WARNING: bootm_low + bootm_size exceed eff. memory

And I asked:

What exactly are your environment settings (and why did you set
these like that) ?

Either you are using variables like "bootm_low", and I want to know
their settings and what your reasons for these specific settings are,
or there is a problem with your port.


> > > will ramdisk image from eldk 4.2 work with linux 2.6.34?
> > > will ramdisk image build from RFSB project work with linux 2.6.34?
> > 
> > Yes to both questions - assuming your system configuration is correct,
> > and matches the configuration/assumptions built into these.
> it's good

If it was good, it would be working...

> U-Boot 2009.01-5.adv (Jul 13 2010 - 15:49:10)
> 
> CPU:   AMCC PowerPC 460GT Rev. A at 666.667 MHz (PLB=166, OPB=83, EBC=83 MHz)
>        Security/Kasumi support
>        Bootstrap Option H - Boot ROM Location I2C (Addr 0x52)
>        32 kB I-Cache 32 kB D-Cache
> Board: Transcend 800 R3 - AdvantechAMT PPC460GT Board

OK, so this is an old (1.5 years is actually very old) out-of-tree
port.  Please consider it unsupported.

> I2C:   ready
> DRAM:   1 GB
> Top of RAM usable for U-Boot at: 3f072000

Where is the 0x3f072000 coming from? What's above this?

...
> => printenv
> bootcmd=run default_boot
> bootdelay=7
> baudrate=115200
> loads_echo=
> ethaddr=02:2E:02:08:FF:00
> eth1addr=02:2E:02:08:FF:01
> eth2addr=02:2E:02:08:FF:02
> eth3addr=02:2E:02:08:FF:03
> ipaddr=192.168.12.20
> serverip=192.168.12.5
> hostname=t800
> preboot=echo;echo;echo
> netdev=eth0
> ethprime=ppc_4xx_eth0
> hostname=t800
> mtdids=nand0=nand0
> mtdparts=mtdparts=nand0:1m(boot),7m(loader),48m(software),8m(data)
> partition=nand0,2
> mtddevnum=2
> mtddevname=software
> boot0=chpart nand0,1;fsload 8000000 boot-image;bootm 8000000;reset
> bootname0=loader
> boot1=chpart nand0,2;fsload 8000000 boot-image;bootm 8000000;chpart nand0,1;fsload 8000000 boot-image;bootm 8000000;reset
> bootname1=software
> default_boot=chpart nand0,2;fsload 8000000 boot-image;bootm 8000000;chpart nand0,1;fsload 8000000 boot-image;bootm 8000000;reset
> default_bootname=software
> bootargs=root=/dev/ram rw console=ttyS2,115200
> ll=tftp 400000 t800.dts;tftp 408000 uImage;tftp 600000 uRamdisk;bootm 408000 600000 400000
> stdin=serial
> stdout=serial
> stderr=serial
> ethact=ppc_4xx_eth0
> ver=U-Boot 2009.01-5.adv (Jul 13 2010 - 15:49:10)
> 
> Environment size: 1065/16379 bytes
> Environment pointer: 0x3f004000
> Environment address: 0x3f004005
> Environment valid: 1

Ah! so there are no definitions of "bootm_low" and/or "bootm_size" -
which means there are issues with your U-Boot port.


Also note that there are chances that you will overwrite your device
tree. Move it to a higher location, i. e. after the ramdisk image.

...
> Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> serial8250.0: ttyS0 at MMIO 0x4ef600300 (irq = 19) is a 16550A
> serial8250.0: ttyS1 at MMIO 0x4ef600400 (irq = 20) is a 16550A
> serial8250.0: ttyS2 at MMIO 0x4ef600500 (irq = 29) is a 16550A
> console [ttyS2] enabled, bootconsole disabled
> console [ttyS2] enabled, bootconsole disabled
> serial8250.0: ttyS3 at MMIO 0x4ef600600 (irq = 21) is a 16550A
> 4ef600300.serial: ttyS0 at MMIO 0x4ef600300 (irq = 19) is a 16550
> 4ef600400.serial: ttyS1 at MMIO 0x4ef600400 (irq = 20) is a 16550
> 4ef600500.serial: ttyS2 at MMIO 0x4ef600500 (irq = 29) is a 16550
> 4ef600600.serial: ttyS3 at MMIO 0x4ef600600 (irq = 21) is a 16550

This looks OK, so check your ramdisk settings.

Eventually you might consider using CONFIG_DEVTMPFS ...

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Advice is seldom welcome; and those who want it the most always like
it the least.                         -- Philip Earl of Chesterfield