2009-08-10 09:41:43 2008R1 with Virtual Terminal and Framebuffer Console Support issues

Patrick Hotz (GERMANY)

Message: 78560

Hi,

i want to test microwindows with our display-driver without Framebuffer Console Support.

I have tested two versions of settings:

First i have enabled

"Character devices => Virtual Terminal => Support for console on virtual terminal" and

"Graphics Support => Console Display driver support => Framebuffer Console support"

With this options i can run "nano-X" without problems...

But with this configuration the frame-buffer is always transferred to the external hardware....and this i want to prevent.

The second configuration is without "Virtual Terminal" and without "Console Display driver support",

that means i have to flush the firtual framebuffer manually to my display-chip.

There is the problem that nano-X wants to initialise more than 255 Colorregions and chrashes the kernel

My question is following:

Is it possible to run nano-X without a "Virtual Terminal" ?

..................

s1d13513fb_setcolreg(): regno=F9h red=0000h green=0000h blue=0000h transp=FFFFh

s1d13513fb_setcolreg(): regno=FAh red=0000h green=0000h blue=0000h transp=FFFFh

s1d13513fb_setcolreg(): regno=FBh red=0000h green=0000h blue=0000h transp=FFFFh

s1d13513fb_setcolreg(): regno=FCh red=0000h green=0000h blue=0000h transp=FFFFh

s1d13513fb_setcolreg(): regno=FDh red=0000h green=0000h blue=0000h transp=FFFFh

s1d13513fb_setcolreg(): regno=FEh red=0000h green=0000h blue=0000h transp=FFFFh

s1d13513fb_setcolreg(): regno=FFh red=0000h green=0000h blue=0000h transp=FFFFh

Going to reboot

Data access misaligned address violation

- Attempted misaligned data memory or data cache access.

Kernel OOPS in progress

Defered Exception context

No Valid process in current context

return address: [0x00108220]; contents of:

0x00108200: 030c 539e 1802 67fe e801 0000 3005 300e

0x00108210: 05ad 0010 3210 0578 e800 0000 3011 6003

0x00108220: [e410] 0041 5008 e610 0041 e121 0078 a210

0x00108230: 0908 1c12 e14a 002c e10a f448 a090 a0d1

SEQUENCER STATUS: Not tainted

SEQSTAT: 00002024 IPEND: 2030 SYSCFG: 0006

HWERRCAUSE: 0x0

EXCAUSE : 0x24

physical IVG13 asserted : <0xffa01378> { _evt_evt13 + 0x0 }

logical irq 6 mapped : <0xffa00260> { _timer_interrupt + 0x0 }

logical irq 12 mapped : <0xffa024cc> { _AudioRxPPI_ERR + 0x0 }

logical irq 16 mapped : <0x001dfeb8> { _bfin_twi_interrupt_entry + 0x0 }

logical irq 18 mapped : <0x001b7b90> { _bfin_serial_rx_int + 0x0 }

logical irq 19 mapped : <0x001b7d78> { _bfin_serial_tx_int + 0x0 }

logical irq 20 mapped : <0x001b7b90> { _bfin_serial_rx_int + 0x0 }

logical irq 21 mapped : <0x001b7d78> { _bfin_serial_tx_int + 0x0 }

logical irq 24 mapped : <0x001c6504> { _bf537mac_interrupt + 0x0 }

logical irq 40 mapped : <0x001d032c> { _AudioDataISR + 0x0 }

logical irq 66 mapped : <0x001dd130> { _tsc2003_irq + 0x0 }

RETE: <0x00000000> /* Maybe null pointer? */

RETN: <0x02205e88> /* unknown address */

RETX: <0x00108220> { _account_user_time + 0xc }

RETS: <0x0011340e> { _update_process_times + 0x1e }

PC : <0x00108220> { _account_user_time + 0xc }

DCPLB_FAULT_ADDR: <0x0000a744> /* Maybe null pointer? */

ICPLB_FAULT_ADDR: <0x00108220> { _account_user_time + 0xc }

PROCESSOR STATE:

R0 : 0000a641 R1 : 00000001 R2 : 00000001 R3 : 00000000

R4 : 00000000 R5 : 00000006 R6 : 00000001 R7 : 0000a641

P0 : 002d6690 P1 : 00000000 P2 : 0000a641 P3 : 002d8640

P4 : 00000006 P5 : 002d6680 FP : 02205e88 SP : 02205dac

LB0: 03466181 LT0: 03466174 LC0: 00000000

LB1: 023063f3 LT1: 023063d4 LC1: 0000aca1

B0 : 00000000 L0 : 00000000 M0 : 00000000 I0 : 00000001

B1 : 00000000 L1 : 00000000 M1 : 00000000 I1 : 00000000

B2 : 00000000 L2 : 00000000 M2 : 00000000 I2 : 00000000

B3 : 00000000 L3 : 00000000 M3 : 00000000 I3 : 00000000

A0.w: 00000000 A0.x: 00000000 A1.w: 00000000 A1.x: 00000000

USP : 0235fd00 ASTAT: 02003004

Hardware Trace:

0 Target : <0x001037be> { _trap_c + 0x1e }

Source : <0x0010c14e> { _printk + 0x16 }

1 Target : <0x0010c14a> { _printk + 0x12 }

Source : <0x0010c000> { _vprintk + 0x1b8 }

2 Target : <0x0010bff4> { _vprintk + 0x1ac }

Source : <0x0010bfe6> { _vprintk + 0x19e }

3 Target : <0x0010bfe2> { _vprintk + 0x19a }

Source : <0x0010be30> { _wake_up_klogd + 0x24 }

4 Target : <0x0010be0c> { _wake_up_klogd + 0x0 }

Source : <0x0010c538> { _release_console_sem + 0x1f4 }

5 Target : <0x0010c52a> { _release_console_sem + 0x1e6 }

Source : <0x0010c51c> { _release_console_sem + 0x1d8 }

6 Target : <0x0010c512> { _release_console_sem + 0x1ce }

Source : <0x0010c504> { _release_console_sem + 0x1c0 }

7 Target : <0x0010c4e4> { _release_console_sem + 0x1a0 }

Source : <0x0010c3ca> { _release_console_sem + 0x86 }

8 Target : <0x0010c39a> { _release_console_sem + 0x56 }

Source : <0x0010c4c6> { _release_console_sem + 0x182 }

9 Target : <0x0010c4c0> { _release_console_sem + 0x17c }

Source : <0x0010bd06> { __call_console_drivers + 0x7e }

10 Target : <0x0010bd00> { __call_console_drivers + 0x78 }

Source : <0x0010bcc2> { __call_console_drivers + 0x3a }

11 Target : <0x0010bcb2> { __call_console_drivers + 0x2a }

Source : <0x0010bca2> { __call_console_drivers + 0x1a }

12 Target : <0x0010bc88> { __call_console_drivers + 0x0 }

Source : <0x0010c4bc> { _release_console_sem + 0x178 }

13 Target : <0x0010c4b2> { _release_console_sem + 0x16e }

Source : <0x0010c450> { _release_console_sem + 0x10c }

14 Target : <0x0010c44a> { _release_console_sem + 0x106 }

Source : <0x0010bc86> { ___call_console_drivers + 0x52 }

15 Target : <0x0010bc7a> { ___call_console_drivers + 0x46 }

Source : <0x001b7742> { _bfin_serial_console_write + 0x46 }

Stack from 02205d8c:

00000000 ffa00780 0029e628 0029e628 0029e624 00000000 00000000 00000000

00108220 00002030 00002024 00000000 02205e88 00108220 00108220 0011340e

0000a641 02003004 023063f3 03466181 023063d4 03466174 0000aca1 00000000

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 00000000 00000001 0235fd00 02205e88 002d6680 00000006

Call Trace:

[<0011340e>] _update_process_times+0x1e/0x54

[<00125f58>] _handle_IRQ_event+0x34/0x5c

[<00126f24>] _handle_simple_irq+0x44/0x94

Modules linked in:

Kernel panic - not syncing: Kernel exception

TranslateQuoteReplyEditDelete

2009-08-11 06:05:08 Re: 2008R1 with Virtual Terminal and Framebuffer Console Support issues

Patrick Hotz (GERMANY)

Message: 78613

Hi,

i have tested some modifications in my display driver and in nano-X.

I have found out that the problem is the "GdSetPalette" in nano-X (devopen.c).

Without that function the nano-X is starting ok and i can run some demos like "demo", "demo2".

Also i have enabled the tslib touchscreen.

This is also working and i can see a mouse that i can move on the black screen of nano-X.

But the problem with colorregions is still there,

if i start for example "tuxchess" the program wants to set some colorregios (use driver-function .fb_setcolreg).

If i enable the display-console support is works....

Does nobody knows if there is a way without display-console support

Patrick

TranslateQuoteReplyEditDelete

2009-08-11 11:07:43 Re: 2008R1 with Virtual Terminal and Framebuffer Console Support issues

Patrick Hotz (GERMANY)

Message: 78664

OK,

forget my first two posts,

i think there is a bug in microwindows nano-X...

i i select MWPF_TRUECOLOR565 in config the nano-x initialishes MWPF_PALETTE !!!!!!!!!!

I have tested that in function GdSetPalette(PSD psd, int first, int count, MWPALENTRY *palette) in file devopen.c from nano-x.

In config there is set SCREEN_PIXTYPE = MWPF_TRUECOLOR565

Any idea?

Partner Forums

Partner Libraries

2009-08-10 09:41:43 2008R1 with Virtual Terminal and Framebuffer Console Support issues