[SF] Repository Update 25/09/12

[Tony Prisk]

I have uploaded another tarball with the current WMT branch. (linuxwmt-12-09-25.tar.bz2)

Given that the git fetch instructions and build instructions are in the wiki, I expect this will be the last tarball.
Creating tarball's for users is, well, annoying and unnecessary.

I recommend you try getting the git source instead - if you can't, let me know and I'll try help.
It makes updates much easier and means you can have the current source as soon as it's pushed.

Regards

Tony P

[J T Dsouza]

Followed the wiki and ended with * wmt.

Compiled the image as per the wiki. The image boots from microsd and
usb but no display.
The earlier tar ball you provided always produced a display, but
failed to mount rootfs. from
either microsd or usb.

[Tony Prisk]

Do you have a 7" WM8650-based tablet? I assume so since you say it
worked on the tarball.

If so, I can't see any reason why it shouldn't have a display.
I *think* the driver changed between the 12-09-01 tarball and the
current git, but most of my testing is done on a 7" WM8650 so it should
'just work'.

Do you see any framebuffer related output in dmesg via serial?

Regards

Tony P

[J T Dsouza]

On Tue, Sep 25, 2012 at 9:18 AM, Tony Prisk <li...@prisktech.co.nz> wrote:
> On Tue, 2012-09-25 at 03:49 +0530, J T Dsouza wrote:
>> Followed the wiki and ended with * wmt.
>>
>> Compiled the image as per the wiki. The image boots from microsd and
>> usb but no display.
>> The earlier tar ball you provided always produced a display, but
>> failed to mount rootfs. from
>> either microsd or usb.
>>
>> On Tue, Sep 25, 2012 at 2:07 AM, Tony Prisk
>> <sent...@digitalfantasy.co.nz> wrote:
>> > I have uploaded another tarball with the current WMT branch.
>> > (linuxwmt-12-09-25.tar.bz2)
>> >
>> > Given that the git fetch instructions and build instructions are in the
>> > wiki, I expect this will be the last tarball.
>> > Creating tarball's for users is, well, annoying and unnecessary.
>> >
>> > I recommend you try getting the git source instead - if you can't, let me
>> > know and I'll try help.
>> > It makes updates much easier and means you can have the current source as
>> > soon as it's pushed.
>> >
>> > Regards
>> >
>> > Tony P
>
> Do you have a 7" WM8650-based tablet?

yes

> I assume so since you say it worked on the tarball.

display worked, though sdmmc and usb did not.

>
> If so, I can't see any reason why it shouldn't have a display.
> I *think* the driver changed between the 12-09-01 tarball and the
> current git, but most of my testing is done on a 7" WM8650 so it should
> 'just work'.
>
> Do you see any framebuffer related output in dmesg via serial?

Dump of console
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.6.0-rc6+ (root@debamd) (gcc version
4.4.5 (Debian 4.4.5-8) ) #2 Tue Sep 25 03:21:57 IST 2012
[ 0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine: VIA/Wondermedia SoC (Device Tree Support),
model: Wondermedia WM8650-MID Tablet
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 54356
[ 0.000000] Kernel command line: mem=214M root=/dev/mmcblk0p2
noinitrd rw rootfstype=ext2 console=ttyWMT0,115200n8 consol0
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Memory: 214MB = 214MB total
[ 0.000000] Memory: 211336k/211336k available, 7800k reserved, 0K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xcd800000 - 0xff000000 ( 792 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xcd600000 ( 214 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc04f9070 (5061 kB)
[ 0.000000] .init : 0xc04fa000 - 0xc051fb84 ( 151 kB)
[ 0.000000] .data : 0xc0520000 - 0xc0556a98 ( 219 kB)
[ 0.000000] .bss : 0xc0556abc - 0xc05adf38 ( 350 kB)
[ 0.000000] NR_IRQS:128
[ 0.000000] Added IRQ Controller @ f8140000 [virq_base = 0]
[ 0.000000] Added IRQ Controller @ f8150000 [virq_base = 64]
[ 0.000000] vt8500-irq: Enabled slave->parent interrupts
[ 0.000000] sched_clock: 32 bits at 100 Hz, resolution 10000000ns,
wraps every 4294967286ms
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] console [tty1] enabled
[ 0.060000] Calibrating delay loop... 298.59 BogoMIPS (lpj=1492992)
[ 0.070000] pid_max: default: 32768 minimum: 301
[ 0.070000] Security Framework initialized
[ 0.070000] Mount-cache hash table entries: 512
[ 0.070000] Initializing cgroup subsys cpuacct
[ 0.070000] Initializing cgroup subsys devices
[ 0.070000] Initializing cgroup subsys freezer
[ 0.070000] Initializing cgroup subsys net_cls
[ 0.070000] CPU: Testing write buffer coherency: ok
[ 0.070000] Setting up static identity map for 0x3ac8c8 - 0x3ac920
[ 0.070000] devtmpfs: initialized
[ 0.080000] dummy:
[ 0.080000] NET: Registered protocol family 16
[ 0.080000] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.080000] No ATAGs?
[ 0.090000] bio: create slab <bio-0> at 0
[ 0.090000] SCSI subsystem initialized
[ 0.090000] usbcore: registered new interface driver usbfs
[ 0.090000] usbcore: registered new interface driver hub
[ 0.090000] usbcore: registered new device driver usb
[ 0.100000] Switching to clocksource vt8500_timer
[ 0.150000] NET: Registered protocol family 2
[ 0.150000] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.150000] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.150000] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.150000] TCP: reno registered
[ 0.150000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.150000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.160000] NET: Registered protocol family 1
[ 0.160000] NetWinder Floating Point Emulator V0.97 (double precision)
[ 0.160000] audit: initializing netlink socket (disabled)
[ 0.160000] type=2000 audit(0.160:1): initialized
[ 0.340000] VFS: Disk quotas dquot_6.5.2
[ 0.340000] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.340000] jffs2: version 2.2. (NAND) (SUMMARY) �© 2001-2006 Red Hat, Inc.
[ 0.340000] msgmni has been set to 412
[ 0.340000] Block layer SCSI generic (bsg) driver version 0.4
loaded (major 252)
[ 0.340000] io scheduler noop registered
[ 0.340000] io scheduler deadline registered
[ 0.340000] io scheduler cfq registered (default)
[ 0.340000] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.350000] d8200000.uart: ttyWMT0 at MMIO 0xd8200000 (irq = 32) is
a VT8500 UART-1
[ 0.750000] console [ttyWMT0] enabled
[ 0.750000] d82b0000.uart: ttyWMT1 at MMIO 0xd82b0000 (irq = 33) is
a VT8500 UART-1
[ 0.760000] GPIO NAND driver, �© 2004 Simtec Electronics
[ 0.770000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.770000] uhci_hcd: USB Universal Host Controller Interface driver
[ 0.780000] platform-uhci d8007b00.uhci: Generic UHCI Host Controller
[ 0.790000] platform-uhci d8007b00.uhci: new USB bus registered,
assigned bus number 1
[ 0.790000] platform-uhci d8007b00.uhci: irq 43, io mem 0xd8007b00
[ 0.800000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
[ 0.810000] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 0.810000] usb usb1: Product: Generic UHCI Host Controller
[ 0.820000] usb usb1: Manufacturer: Linux 3.6.0-rc6+ uhci_hcd
[ 0.830000] usb usb1: SerialNumber: d8007b00.uhci
[ 0.830000] hub 1-0:1.0: USB hub found
[ 0.830000] hub 1-0:1.0: 2 ports detected
[ 0.840000] Initializing USB Mass Storage driver...
[ 0.840000] usbcore: registered new interface driver usb-storage
[ 0.850000] USB Mass Storage support registered.
[ 0.860000] mousedev: PS/2 mouse device common for all mice
[ 0.860000] cpuidle: using governor ladder
[ 0.860000] cpuidle: using governor menu
[ 0.870000] sdhci: Secure Digital Host Controller Interface driver
[ 0.870000] sdhci: Copyright(c) Pierre Ossman
[ 0.880000] usbcore: registered new interface driver ushc
[ 0.880000] vt8500_dclk_set_rate: invalid divisor for clock
[ 0.890000] vt8500_dclk_set_rate: invalid divisor for clock
[ 0.910000] vt8500_dclk_set_rate: invalid divisor for clock
[ 0.930000] [MMC/SD] WMT MCI Controller (DriverVersion=13)
[ 0.930000] sdhci-pltfm: SDHCI platform and OF driver helper
[ 0.940000] vt8500_dclk_set_rate: invalid divisor for clock
[ 0.940000] vt8500_dclk_set_rate: invalid divisor for clock
[ 0.950000] vt8500_dclk_set_rate: invalid divisor for clock
[ 0.950000] vt8500_dclk_set_rate: invalid divisor for clock
[ 0.960000] drop_monitor: Initializing network drop monitor service
[ 0.960000] TCP: cubic registered
[ 0.970000] vt8500_dclk_set_rate: invalid divisor for clock
[ 0.970000] vt8500_dclk_set_rate: invalid divisor for clock
[ 0.980000] NET: Registered protocol family 10
[ 0.980000] mip6: Mobile IPv6
[ 0.990000] vt8500_dclk_set_rate: invalid divisor for clock
[ 0.990000] vt8500_dclk_set_rate: invalid divisor for clock
[ 1.000000] NET: Registered protocol family 17
[ 1.000000] VFP support v0.3: not present
[ 1.010000] vt8500_dclk_set_rate: invalid divisor for clock
[ 1.010000] vt8500_dclk_set_rate: invalid divisor for clock
[ 1.020000] registered taskstats version 1
[ 1.020000] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 1.030000] Waiting 10sec before mounting root device...
[ 1.030000] vt8500_dclk_set_rate: invalid divisor for clock
[ 1.040000] vt8500_dclk_set_rate: invalid divisor for clock
[ 1.040000] vt8500_dclk_set_rate: invalid divisor for clock
[ 1.050000] vt8500_dclk_set_rate: invalid divisor for clock
[ 1.060000] vt8500_dclk_set_rate: invalid divisor for clock
[ 1.060000] vt8500_dclk_set_rate: invalid divisor for clock
[ 1.070000] vt8500_dclk_set_rate: invalid divisor for clock
[ 1.070000] vt8500_dclk_set_rate: invalid divisor for clock
[ 1.080000] vt8500_dclk_set_rate: invalid divisor for clock
[ 1.080000] vt8500_dclk_set_rate: invalid divisor for clock
[ 1.110000] vt8500_dclk_set_rate: invalid divisor for clock
[ 1.110000] vt8500_dclk_set_rate: invalid divisor for clock
[ 1.120000] vt8500_dclk_set_rate: invalid divisor for clock
[ 1.120000] vt8500_dclk_set_rate: invalid divisor for clock
[ 1.130000] mmc0: new high speed SDHC card at address 1234
[ 1.130000] mmcblk0: mmc0:1234 SA04G 3.65 GiB
[ 1.140000] mmcblk0: p1 p2
[ 11.040000] 11.730000] VFS: Mounted root (ext2 filesystem) on device 179:2.
[ 11.730000] Freeing init memory: 148K

>
> Regards
>
> Tony P
>

[J T Dsouza]

and the uboot setenv string

setenv bootargs 'mem=214M root=/dev/mmcblk0p2 noinitrd rw
rootfstype=ext2 console=ttyWMT0,115200n8 console=tty1 rootdelay=10'

just incase i am missing something here.

[Alexey Charkov]

Any difference if you remove mem= argument?

[J T Dsouza]

On Tue, Sep 25, 2012 at 11:05 AM, Alexey Charkov <alc...@gmail.com> wrote:
> Any difference if you remove mem= argument?

None.

[Alexey Charkov]

Can you share your .config then?

Best,
Alexey

2012/9/25 J T Dsouza <jtd...@gmail.com>:

[Tony Prisk]

Two things stand out

1) You need to increase the coherent memory allocation - you are only
reserving 256KB for coherent allocations. Increase it to at least 2MB
for the framebuffer - more doesn't really hurt, it's still available for
normal allocations - I think mine is on 16MB. This should give an error
message if its a problem.

2) The graphics driver isn't showing any messages at all. Either the
devicetree isn't configured correctly (I would hope it is) or the driver
isn't selected in .config.

One thing that pop's to mind is to check the devicetree
(arch/arm/boot/dts/wm8650.dtsi) compatible string = 'wm,wm8650-fb'

Regards

Tony P

[J T Dsouza]

attached

[Tony Prisk]

As I said in my other message:

2) The graphics driver isn't showing any messages at all. Either the
devicetree isn't configured correctly (I would hope it is) or the

**driver isn't selected in .config**.

In .config:
# CONFIG_FB_WMT is not set
# CONFIG_FB_WMT_GE_ROPS is not set

Try adding:
Device Drivers->Graphics Support->Support for framebuffer
devices->Wondermedia SoC framebuffer Support
Device Drivers->Graphics Support->Support for framebuffer
devices->Enable Wondermedia GE Acceleration

And you should be right.

Regards

Tony P

[J T Dsouza]

Ok, But I am quite sure no such option appeared. But I will redo. No
shortcuts - mrpoper :-(.

[Tony Prisk]

If the option isn't there, let me know - might be something I need to
look at. You should have it easier than a few others as you have the
same hardware I do most of my testing on :)

Regards

Tony P

[J T Dsouza]

On Tue, Sep 25, 2012 at 1:05 PM, Tony Prisk <li...@prisktech.co.nz> wrote:
> On Tue, 2012-09-25 at 11:32 +0530, J T Dsouza wrote:
>> On Tue, Sep 25, 2012 at 11:05 AM, Alexey Charkov <alc...@gmail.com> wrote:
>> > Any difference if you remove mem= argument?

> Two things stand out
>
> 1) You need to increase the coherent memory allocation - you are only
> reserving 256KB for coherent allocations. Increase it to at least 2MB
> for the framebuffer - more doesn't really hurt, it's still available for
> normal allocations - I think mine is on 16MB. This should give an error
> message if its a problem.

Is CMA applicable to ARMV6+.and above? If so will I have to use
something else instead of -march=armv4t -mtune=arm920t

What should I change in .config

[Alexey Charkov]

2012/9/27 J T Dsouza <jtd...@gmail.com>:

> On Tue, Sep 25, 2012 at 1:05 PM, Tony Prisk <li...@prisktech.co.nz> wrote:
>> On Tue, 2012-09-25 at 11:32 +0530, J T Dsouza wrote:
>>> On Tue, Sep 25, 2012 at 11:05 AM, Alexey Charkov <alc...@gmail.com> wrote:
>>> > Any difference if you remove mem= argument?
>
>> Two things stand out
>>
>> 1) You need to increase the coherent memory allocation - you are only
>> reserving 256KB for coherent allocations. Increase it to at least 2MB
>> for the framebuffer - more doesn't really hurt, it's still available for
>> normal allocations - I think mine is on 16MB. This should give an error
>> message if its a problem.
>
> Is CMA applicable to ARMV6+.and above? If so will I have to use
> something else instead of -march=armv4t -mtune=arm920t
>
> What should I change in .config

I think that this dependency has been relaxed recently to also cover
ARMv5. Isn't it just a matter of appending coherent_pool=[size] to the
kernel command line?

Best,
Alexey

[J T Dsouza]

Attached the new .config. No console or screen.

setenv bootargs 'mem=214M root=/dev/mmcblk0p2 noinitrd rw
rootfstype=ext2 console=ttyWMT0,115200n8 console=tty1 rootdelay=10

panel=800x480 coherent_pool=2000000'

And various combinations of the above.

Downloading the new tarball. will know if it's just me being stupid or
git playing truant.

[J T Dsouza]

The downloaded tarball compiled and boots from mmc and gives me a
login, but not from usb. Usb plug events are not discovered. USB is
compiled into kernel. So no keyboard.
have to check what driver will work in place of rt3070sta. Afaik it is
replaced by rt5070.

Looks like git errs.
I will use the new .config on the sources from git and verify.

[Tony Prisk]

CMA is for coherent-memory-allocations and is required for allocating
the framebuffer (rather than reserving it early). You can set the
coherent reservation size @:
Device Drivers->Generic Driver Options->Contiguous Memory Allocator [*]
Device Drivers->Generic Driver Options->Size in Mega bytes [16]

[Alexey Charkov]

2012/9/28 Tony Prisk <sent...@digitalfantasy.co.nz>:

Would it make sense to add some sort of Kconfig dependency on these
for the framebuffer driver, or at least make it print explicit
suggestions upon allocation failure?

Best,
Alexey

[Tony Prisk]

Its weird, but quite often I can have CMA disabled and it will still
work :) Other times, it gives a -NOMEM fault. I guess it just depends on
which options are enabled and where the memory gets allocated from.

I need to patch the framebuffer code for 3.8, so I'll add a more
explicit message for framebuffer memory allocation failures.

Regards

Tony P

[Marcos Silva Cunha]

Also I have pulled last repo state as it says on Wiki, but got everything different (nothing about "GE acceleration", only "WM8505 fb support" and "VT8500 LCD driver" under "Support for fb devices"). Fact: display doesn't work for me using the SF's git repo, only with gitorious.

[Tony Prisk]

When did you pull it?

If it was in the last day or two, then...

I have updated the config instructions on the wiki to reflect the fact
that I pulled past v3.6 in mainline and so it includes the new device
tree files from mainline (the latest patchset I sent to -next).

Mainline doesn't include the new WM8505 driver that *was* in the wmt
branch. As a result (and as mentioned in the git log), the new driver
was dropped and replaced with the mainline version (the old one) and the
config instructions were changed accordingly.

So yes, you are correct - only vt8500 and wm8505 framebuffers are now
available - no seperate GE acceleration. The wiki reflects this.

If you join the linuxwmt project on sourceforge, you would recieve
notifications of changes (to the downloads and wiki at least - I don't
think git updates result in email notifications).

As for it not working... I'll pull the sourceforge code down into a
clean directory and test it on my wm8650.

Regards

Tony P

[Tony Prisk]

I pulled the source down into a clean directory, and compiled.

I found two problems:
1) There was a unresoved merge conflict in wm8650.dtsi which prevented
it from compiling. I have pushed a fix for this.
2) The UHCI driver has been modified between me submitting it and it
being applied to mainline which results in it not working with attached
devices. I have pushed a fix to WMT.

The display works fine on my wm8650 tablet.

Regards

Tony P

[Marcos Silva Cunha]

Hi Tony, thanks for you attention. I pulled and recompiled my kernel but still no video. I'm attaching my config. These are the commands I run to prepare the MMC:

mkimage -A arm -O linux -T script -C gzip -a 1 -e 0 -n "Script" -d wmt_script.source wmt_scriptcmd 

make mrproper

make distclean

make ARCH=arm menuconfig

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage -j5

cp arch/arm/boot/uImage /media/MMC2GB_P1/

umount /dev/sdc*

Regards,

On Monday, 24 September 2012 17:37:32 UTC-3, Tony Prisk wrote:

[Tony Prisk]

Straight away I can see that you haven't followed/understoof the
instructions on the wiki.

1) Where is the dtb being compiled? (This only needs to be done once
unless you change it so understandable that its not in the script).
2) Where is the dtb being appended to the image? (This needs to be done
everytime you rebuild zImage).

Step 4 and 5 from the wiki:
=====
4) Build the devicetree files (<-- my point 1) above).
Select one of the following files based on your target device.
make ARCH=arm vt8500-bv07.dtb
make ARCH=arm wm8505-ref.dtb
make ARCH=arm wm8650-mid.dtb

5) Build the image <-- my point 2) above)
cat arch/arm/boot/zImage arch/arm/boot/wm8650-mid.dtb >
arch/arm/boot/zImage_w_dtb
replace wm8650-mid.dtb with the appropriate file from step 3

mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -n "My
Linux" -d arch/arm/boot/zImage_w_dtb ~/uzImage.bin
=====

It would appear you are missing 2 steps in the build process.

Regards

Tony P

[Marcos Silva Cunha]

Thanks for the instructions, even I'm not aware of the device-tree-stuff. I did the following commands:

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- wm8650-mid.dtb

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- zImage -j5

cat arch/arm/boot/zImage arch/arm/boot/wm8650-mid.dtb > arch/arm/boot/zImage_w_dtb

mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -n "MyLinux" -d arch/arm/boot/zImage_w_dtb arch/arm/boot/uzImage.out

cp arch/arm/boot/uzImage.out /media/MMC2GB_P1/uImage

And it still without video.

Could you give a little explanation about the differences of the device-tree-style and the old-fashion (compile, copy image, boot)?

Also, my wmt_script.source

display init force

mmcinit 0

fatload mmc 0 0 uImage

setenv bootargs 'root=/dev/mmcblk0p2 rootwait console=tty0 console=tty1 panel=800x480 mem=214M'

bootm 0

And the line that compiles it:

mkimage -A arm -O linux -T script -C gzip -a 1 -e 0 -n "Script" -d wmt_script.source wmt_scriptcmd

Regards,

On Monday, 24 September 2012 17:37:32 UTC-3, Tony Prisk wrote:

[Tony Prisk]

On Thu, 2012-10-04 at 14:12 -0700, Marcos Silva Cunha wrote:
> Thanks for the instructions, even I'm not aware of the
> device-tree-stuff. I did the following commands:
>
>
> make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- wm8650-mid.dtb
> make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- zImage -j5
>
> cat arch/arm/boot/zImage arch/arm/boot/wm8650-mid.dtb >
> arch/arm/boot/zImage_w_dtb
>
> mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -n
> "MyLinux" -d arch/arm/boot/zImage_w_dtb arch/arm/boot/uzImage.out
> cp arch/arm/boot/uzImage.out /media/MMC2GB_P1/uImage
>
>
>
> And it still without video.
>
>
> Could you give a little explanation about the differences of the
> device-tree-style and the old-fashion (compile, copy image, boot)?
>
>
> Also, my wmt_script.source
>
>
> display init force

I use lcdinit here, but this might work - first time I've seen it.

> mmcinit 0
> fatload mmc 0 0 uImage
> setenv bootargs 'root=/dev/mmcblk0p2 rootwait console=tty0

I don't have a console= command, so presumably you don't need it. Also,
on arch-vt8500, our tty's are WMTtty0 if you are redirecting.
> console=tty1 panel=800x480 mem=214M'
I don't believe panel= will do anything here.

> bootm 0
>
>
> And the line that compiles it:
>
>
> mkimage -A arm -O linux -T script -C gzip -a 1 -e 0 -n "Script" -d
> wmt_script.source wmt_scriptcmd
>
>
>
> Regards,
>
> On Monday, 24 September 2012 17:37:32 UTC-3, Tony Prisk wrote:
> I have uploaded another tarball with the current WMT branch.
> (linuxwmt-12-09-25.tar.bz2)
>
> Given that the git fetch instructions and build instructions
> are in the wiki, I expect this will be the last tarball.
> Creating tarball's for users is, well, annoying and
> unnecessary.
>
> I recommend you try getting the git source instead - if you
> can't, let me know and I'll try help.
> It makes updates much easier and means you can have the
> current source as soon as it's pushed.
>
> Regards
>
> Tony P

Here is my current scriptcmd:

lcdinit
textout 30 30 "Booting Linux Image" 0xffffff
fatload mmc 0 0 /script/uzImage.bin
setenv bootargs mem=128M root=/dev/sda1 rootdelay=15
bootm 0

I build it with the following:
mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d scriptcmd.txt
scriptcmd

If you don't have any luck, let me know and I will post a compiled
kernel which you can drop on your mmc and test. If it still won't work
at least we know its either your scriptcmd or an actual bug in the video
code. At the least, I would suggest trying my setenv bootargs line in
place of yours to see if it makes any difference.

Regards

Tony P

[J T Dsouza]

I could not get the display to work at all except with the
linuxwmt-12-09-01.tar.bz2.

Neither git nor the linuxwmt-12-09-25.tar.bz2 worked, although both
would boot completely.
Since I could boot successfully, I also tried to get a login shell on
WMTtty0 /ttyS0 without success.

CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_VT8500_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
# CONFIG_USB_SERIAL_CONSOLE is not set

[Tony Prisk]

I will tar up my current uzImage and scriptcmd for you to test. You can
find it in the downloads on sourceforge once I've done it.

Extract it to your mmc and give it a try - maybe there is an issue with
the driver on your hardware. This seems the easiest way to test it.

Regards

Tony P

[J T Dsouza]

Yes that would be good. Also the .config - if it's not already in the
kernel. Thanks for the effort.

[Marcos Silva Cunha]

lcdinit doesn't work on my tablet and textout is this fashion > textout -1 -1 \"Text\" FFFFFF

Could you tar you current uzImage and send it to us?