From: Ico Doornekamp <fbdev@zevv.nl>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Questions about fbdriver integration
Date: Sun, 25 Nov 2007 13:51:45 +0100 [thread overview]
Message-ID: <20071125125145.GK3183@pruts.nl> (raw)
In-Reply-To: <20071125105153.GH3183@pruts.nl>
* 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.
Thanks for your time,
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/
next prev parent reply other threads:[~2007-11-25 12:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 21:43 Questions about fbdriver integration Ico Doornekamp
2007-11-24 22:09 ` Ico Doornekamp
2007-11-24 22:14 ` Ico Doornekamp
2007-11-24 22:49 ` Jaya Kumar
2007-11-25 9:05 ` Ico Doornekamp
2007-11-25 10:48 ` Jaya Kumar
2007-11-25 10:53 ` Ico Doornekamp
2007-11-25 11:12 ` Jaya Kumar
2007-11-25 11:21 ` Ico Doornekamp
2007-11-28 11:40 ` Ico Doornekamp
2007-11-28 13:00 ` Jaya Kumar
2007-11-28 13:11 ` Jaya Kumar
2007-11-28 13:21 ` Ico Doornekamp
2007-11-25 8:49 ` Geert Uytterhoeven
2007-11-25 10:51 ` Ico Doornekamp
2007-11-25 12:51 ` Ico Doornekamp [this message]
2007-11-25 13:32 ` Questions about fbdriver integration (solved) Ico Doornekamp
2007-11-25 22:17 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071125125145.GK3183@pruts.nl \
--to=fbdev@zevv.nl \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).