Re: Questions about fbdriver integration (solved)

[Ico Doornekamp <fbdev@zevv.nl>]

* On 2007-11-25 Ico Doornekamp <fbdev@zevv.nl> wrote  :

> * On 2007-11-25 Ico Doornekamp <fbdev@zevv.nl> wrote  :
> 
> > > Fbcon writes to the memory at fb_info.screen_base.
> > 
> > That is what I expected. I'll have to do a bit more debugging here then.
> 
> It seems that my driver did not fill the line_length member of
> fb_fix_screeninfo, and no gets was copied by fbcon when this is missing.
> 
> I filled in this field, but now
> 
>   BUG: unable to handle kernel paging request at virtual address c882a800
> 
>   [<c882450c>] mbarcfb_imageblit+0xc/0x20 [mbarcfb]
>   [<c881315d>] soft_cursor+0x15d/0x1bc [softcursor]
>   [<c8817b38>] bit_cursor+0x338/0x5a8 [bitblit]
>   [<c01c5c53>] vsnprintf+0x303/0x690
> 
> happens. Back to do some more debugging.

Ok, one more reply to myself: all problems seem to be solved now - I
changed my driver to support 8-bit pseudocolor instead of 1-bit mono,
and suddenly both the console and X are working just fine. It seems that
the MONO01 visual is just not well supported in various other parts
interacting with the framebuffer code.

The only issue remaining is the kernel warning I posted in an earlier
mail (__set_page_dirty), which I understood Jaya was already trying to
reproduce on his system.

Thank you both for your time and answers,

Ico

-- 
:wq
^X^Cy^K^X^C^C^C^C

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/