From: Antonino D. <ad...@po...> - 2002-11-01 20:08:39
|
On Sat, 2002-11-02 at 03:52, Sven Luther wrote: [...] > > > Ok, i did copy the cfb_ functions to the driver, it works better (the > > > box does not hang anymore), the console apprently works (the cursor > > > blinks in the right place, and it could type stuff, switch VT and > > > shutdown the box) but there is nothing else written. > > > > > > BTW, what is the difference between the full cursor and the underline > > > one ? > > The block cursor most probably comes from fbcon's software cursor, the > > underline is probably your hardware's? > > Mmm, maybe the other way around ? i get block cursor with the old > accelerated pm3fb, and since i did enter no acceleration whatsoever yet > in the new driver, i don't believe it can be using the hardware cursor. > The fbcon software cursor is always a block cursor, well at least before the latest patch James posted. The newest patch should give you an underline cursor by default. > > > Anyway, here are the two Oops : > > > > > > > > [...] > > > I don't believe the result of running ksymoops on these are valid, i > > > will have to reboot in the 2.5.44 kernel for it. > > > > > > > If you did not define fb_set_var at all, then info->disp.dispsw must > > > > point to valid console drawing hooks before you register the > > > > framebuffer. (Actually, all fields in struct display must be valid > > > > before you register the framebuffer) > > > > > > Mmm, still need to check those. > > > > > > > Your oops tracing points to fbcon_cursor as the culprit. If > > > > dispsw->cursor is NULL, then you must have a valid dispsw->revc. > > > > > > There where two oops, the first in fbcon_setup, and the second in > > > fbcon_cursor, i think i will be looking in the first oops first. > > > > > Might as well try to port your driver using the latest fbdev patch > > posted by James, hopefully, this is the last major change. This should > > give you less things to worry about. > > Well, yes, i was going to donwload the BK tree, but james was speaking > about a 2.5.45 diff, which was finally not the right one. > I downloaded the patch 12 hours ago and actually ported a driver to that. So unless James changed it again, it should be the right one. Tony |