Re: [Linux-fbdev-devel] request_mem_region problem ...

[Sven L. <lu...@dp...>]

On Sat, Nov 02, 2002 at 03:42:14AM +0800, Antonino Daplas wrote:
> On Fri, 2002-11-01 at 18:52, Sven Luther wrote:
> > On Thu, Oct 31, 2002 at 07:05:13PM +0800, Antonino Daplas wrote:
> > > Running ksymoops on that might help.  The source can be found at
> > > ftp.kernel.org.  
> > 
> > Ok, got it from the debian package :)))
> > 
> > Erm, i am no more running the same kernel, so i specified the -o and the
> > -m options, but it looks at the wrong /proc/ksyms, should i save the
> > /proc/ksyms of kernel before/after insmodding the pm3fb module ?
> > 
> Save the symbols after the insmod.

Ok,

> > 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.

> > 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.

Will do that nextly.

Friendly,

Sven Luther