Re: [microblaze-uclinux] Setting up framebuffer

Hi,

It does sound ambitious. But nothing is impossible given enough time and patience. Right now I am just trying to run the frame buffer console. But I can not see why you can not run Nano-X if you can access to the fb. The current tools I am using are ISE9.2i, EDK 9.2i and Petalinux2.6 rev0.3. I don't know Petalinux will have GUI support in the plans. You may need to check with John Williams.

regards,

Simon

----- Original Message ----
From: Islam Samir <islambio@xxxxxxxxx>
To: microblaze-uclinux@xxxxxxxxxxxxxx
Cc: amr elwakil <eng_amrelwakil@xxxxxxxxx>
Sent: Tuesday, February 26, 2008 4:39:03 AM
Subject: Re: [microblaze-uclinux] Setting up framebuffer

Hello Simon,

I am really interested in your work to bring up the framebuffer. The problem is that I can't help you because I'm a Newbie in the field of PetaLinux!! We are interested to bring up a GUI using Microblaze and PetaLinux. The first step is to get the Framebuffer up and running. We then plan to use Nano-X on top of it to build a nice GUI on a TFT LCD! Sounds ambitious ?

I need some help to know is this approach feasible or not? Also, which Xilinix kit is recommended to start with? Also, is PetaLinux ready for a GUI or this is not scheduled currently on the plan?

Any help is really appreciated!

Regards,
Islam

Simon Tam <simontam1234@xxxxxxxxx> wrote:

Hi,

            I am still having problem with my frame buffer driver and have some configuration questioins. Attached is bootlog. As far as I can tell, my fb driver has been registered correctly during bootup. I can see the correct physical address put in the structure. I have the frame buffer console enabled also. However I don¢t see anything on the display.

            One of the Linux documents says tty0 can not be used with fb devices. And it seems the first virtual console tty1 should be use instead. Is this correct? If yes I wonder that is the cause of my problem. Although I have the tty1 node in /dev, I can only see vtcon0 under /sys/class/vtconsole. I believe normally I should see vtcon0 all the way to vtcon63, correct? If yes why don¢t I have other vtcons?

Please let me know what I am missing here. I have been struggling with this for a while and really like to get some help.

Thanks,

Simon

#### klimit a8222000 ####

Moving 0x001c1000 bytes from 0xa8200000 to 0xa82214bc

New klimit: 0xa83e3000

Linux version 2.6.20-uc0 (simont@xsjles40) (gcc version 3.4.1 ( PetaLinux 0.20 B

uild -rc1 050607 )) #133 Thu Feb 21 20:07:40 PST 2008

setup_cpuinfo: initialising

setup_cpuinfo: No PVR support in CPU. Using static compile-time info

set_cpuinfo_static: Using static CPU info.

setup_memory: max_mapnr: 0xaffff

setup_memory: min_low_pfn: 0xa8000

setup_memory: max_low_pfn: 0x8000

On node 0 totalpages: 32768

DMA zone: 256 pages used for memmap

DMA zone: 0 pages reserved

DMA zone: 32512 pages, LIFO batch:7

Normal zone: 0 pages used for memmap

Built 1 zonelists. Total pages: 32512

Kernel command line: fbcon=map:0 console=ttyS0, 38400 console=tty1

OPB INTC #0 at 0xC9020000

PID hash table entries: 512 (order: 9, 2048 bytes)

Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)

Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)

Memory: 125824k/131072k available

Calibrating delay loop... 61.64 BogoMIPS (lpj=308224)

Mount-cache hash table entries: 512

NET: Registered protocol family 16

NET: Registered protocol family 2

IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

TCP established hash table entries: 4096 (order: 2, 16384 bytes)

TCP bind hash table entries: 2048 (order: 1, 8192 bytes)

TCP: Hash tables configured (established 4096 bind 2048)

TCP reno registered

io scheduler noop registered

io scheduler anticipatory registered

io scheduler deadline registered

io scheduler cfq registered (default)

acquire_console_sem()

fb_register_client()

fbcon_init_class_device()

Xilinx VGA driver ( Simon Tam )

bus_add_driver() bus: platform driver : xilinxfb

Frame Buffer address : 0xCB800000

Clearing framebuffer

loading FB physical address

Loading FB control registers

Filling struct fb_info

Allocate a colour map

Register new frame buffer

info_idx : 0

fbcon owner : <NULL>

Console: switching to frame buffer device (fbcon)

regs: phys=cb800000, virt=cb800000

fb: phys=ae000000, virt=ae000000, size=1e0000

Creating tty

Creating console

Creating ptmx

Creating tty0

vcs:class_create()

vt:MAX_NR_CONSOLES 63

vt:tty_set_operations()

vt:kbd_init()

vt:console_map_init()

End of tty_io setup

Creating legacy_pty_init

Creating unix98_pty_init

bus_add_driver() bus: platform driver : uartlite

uartlite.0: ttyS0 at MMIO 0xc0000000 (irq = 3) is a uartlite

bus_add_driver() bus: platform driver : mdm-uart

RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize

Microblaze FSL FIFO Driver. John Williams <jwilliams@xxxxxxxxxxxxxx>

FSL FIFO[0] initialised

uclinux[mtd]: RAM probe address=0xa82214bc size=0x1c1000

Creating 1 MTD partitions on "RAM":

0x00000000-0x001c1000 : "ROMfs"

uclinux[mtd]: set ROMfs to be root filesystem index=0

bus_add_driver() bus: platform driver : i8042

i8042.c: i8042 controller self test timeout.

bus_add_driver() bus: serio driver : atkbd

TCP cubic registered

NET: Registered protocol family 1

NET: Registered protocol family 17

VFS: Mounted root (romfs filesystem) readonly.

Freeing unused kernel memory: 112k freed

Mounting proc:

Mounting var:

Populating /var:

Running local start scripts.

Mounting /etc/config:

Populating /etc/config:

flatfsd: Nonexistent or bad flatfs (-48), creating new one...

flatfsd: Failed to write flatfs (-48): No such device

flatfsd: Created 3 configuration files (117 bytes)

Mounting sysfs:

Setting hostname:

Setting up interface lo:

Starting DHCP client:

Jan 1 00:00:02 dhcpcd[42]: dhcpStart: ioctl SIOCGIFHWADDR: No such device

petalinux login:

Looking for last minute shopping deals? Find them fast with Yahoo! Search.