From: Lucas Correia Villa Real <lucasvr@gobolinux.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: bugs!
Date: Fri, 14 May 2004 20:14:40 -0300 [thread overview]
Message-ID: <200405142014.40929.lucasvr@gobolinux.org> (raw)
In-Reply-To: <200405140130.36852.lucasvr@gobolinux.org>
Hi again,
I've fixed the non-linefetch error: I was passing the virtual framebuffer
address into fix.smem_start instead of the physical one. Things got weird
then when fb_writeb() tryied to write on that address ;-)
Cheers,
Lucas
On Friday 14 May 2004 01:30, Lucas Correia Villa Real wrote:
> Hi!
>
> I'm almost finished with my driver for the monochromatic ST7565 LCD, but
> I'm dealing with a bug that I could't solve by the entire day.
>
> It was designed to be run as a module, and it's living together with
> another display that already owns the console devices. So, when I load
> st7565's module, it just skips take_over_console() code in fbmem.c and
> starts to accept write()'s on it.
>
> By the way, I got some demo applications from MicroWindows
> (microwindows.org) that starts to get more information from the driver. It
> looks like when they request st7565_set_cmap(), some invalid pointer is
> accessed and the driver just dies:
>
> Unhandled fault: external abort on non-linefetch (0x00a) at 0x4001a004
> pgd = c3d78000
> *pgd = 0bcaf001, *pmd = 0bcaf001, *pte = c4a5e0b3, *ppte = c4a5eff2
>
> I've looked at other drivers' routines, such as hgafb, and it really looks
> to be everything on the right place. I got the impression that this error
> could be happening due to the fact that my driver didn't get the console's
> ownership, so I've disabled the other driver and compiled st7565 built-in,
> but then the driver dies with the same message at take_over_console().
>
> Does anyone know if hgafb is a working driver that I could rely on? Also I
> got confused by the need to use or not a color pallete -- probably I don't
> need, as I'm working only with black/white, but at this time I'm no more
> sure about anything at all :-)
>
> I'm also confused about the "setcolreg()" function passed to fb_get_cmap().
> What should it do? What's the meaning of its 1st parameter, "regno"?
>
> If someone could take a time to give a quick look on my set_cmap() routine,
> I've uploaded the code here:
>
> http://cscience.org/~lucasvr/etc/st7565.c
>
> Thanks in advance, any help will be very appreciated!
> Lucas
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> _______________________________________________
> Linux-fbdev-devel mailing list
> Linux-fbdev-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
next prev parent reply other threads:[~2004-05-14 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 4:30 bugs! Lucas Correia Villa Real
2004-05-14 23:14 ` Lucas Correia Villa Real [this message]
2004-05-15 2:12 ` bugs! Lucas Correia Villa Real
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=200405142014.40929.lucasvr@gobolinux.org \
--to=lucasvr@gobolinux.org \
--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).