>> In message <1402.194.3.133.184.1148888040.squirrel at webmail.enib.fr> you >> wrote: >>> >>> This seems ok to me but I don't have any video signal. My screen >>> remains >>> blank. >> >> What's your boot arguments? Where is your console device, on the >> serial port or on the frame buffer? > > My boot arguments : > # more /proc/cmdline > console=tty0 console=ttyS1,9600 devfs=mount ip=bootp root=/dev/nfs rw > > My console is on the serial port (ttyS1 on SMC2). > >>> xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory) >>> ... >> >> Did you enable all of the following options in your kernel config? >> >> CONFIG_FB=y >> CONFIG_DUMMY_CONSOLE=y >> CONFIG_FB_MB86290=y >> CONFIG_FBCON_ADVANCED=y >> CONFIG_FBCON_CFB16=y >> CONFIG_FBCON_FONTS=y >> CONFIG_FONT_8x8=y >> CONFIG_FONT_8x16=y >> CONFIG_VT=y >> CONFIG_VT_CONSOLE=y >> >> My guess is that CONFIG_VT and/or CONFIG_VT_CONSOLE might be missing. > > All those options are enabled. >
As I said earlier, when the driver loads, my monitor don't receive any video signal. I can force it by calling at the end of the initialization of the driver : reg = MB86290FB_READ_DISP_REGISTER(GDC_DISP_REG_EXT_MODE); MB86290FB_WRITE_DISP_REGISTER(GDC_DISP_REG_EXT_MODE, reg | 0x80010000); This command enables the display, and "garbage" appears on the monitor. Then if i do : # cat /dev/urandom > /dev/fb0 I should see dummy pixels on the screen but in fact nothing happens. This is still the same garbage on the screen. I use a custom processor card based on a MPC8270. I can't figure out if the problem comes from the configuration of my kernel (all the needed options are enabled) or if it is in the code of the initialisation of my platform. This is the first time I try to use framebuffer graphics, so I'm new with it. Can the framebuffer work from a serial console on a platform without keyboard ? Thanks for your help.
