linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kristoffer Ericson <kristoffer.ericson@gmail.com>
To: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Seg fault on any FB write (Epson S1D13A04onColdfire running 2.6.25)
Date: Thu, 13 Nov 2008 12:55:02 +0100	[thread overview]
Message-ID: <20081113125502.0e43a930.kristoffer.ericson@gmail.com> (raw)
In-Reply-To: <491BEA6A.5060402@cetrtapot.si>


[-- Attachment #1.1: Type: text/plain, Size: 3377 bytes --]

On Thu, 13 Nov 2008 09:50:50 +0100
Hinko Kocevar <hinko.kocevar@cetrtapot.si> wrote:

> James Kimble wrote:
> > 
> > In looking at your driver (which I think is a lot better organized than
> > the general one that came with the kernel by the way) I see that you're
> > doing a whole string of:
> > 
> >                                            ~~~~~~~~~~
> >    device_create_file(&s1d13706fb_device.dev, &dev_attr_reg_0x12);
> >    device_create_file(&s1d13706fb_device.dev, &dev_attr_reg_0x14);
> >    device_create_file(&s1d13706fb_device.dev, &dev_attr_reg_0x16);
> >                                             ~~~~~~~~~~     
> > In  s1d13706fb_init(). I didn't do any of this my driver. Is this needed
> > for any purpose other than to allow easy access to change the values in
> > these registers in user space?
> > 
> 
> It is there purely for debugging purposes. It also allows quick setup of
> eg. different LCD panels that require some tweaking in order to center the
> image or fix refresh rate.
> 
> > I was able to port your driver to the values and registers used by my
> > device and the behavior is virtually the same as with my driver. Screen
> > is initialized, I can see the color palette get set and the panel
> 
> And if you draw a pixel from the driver - does it work? Another quick test
> is to set color palette and then memset() complete framebuffer memory to
> a singles value stored in palette, or change the palette index value to
> achieve image color change on the screen.
> 
> > enable. Everything boots up fine but none of my user space applications
> > work. The first time I try to write to a register or video memory I get
> > a seg fault.
> > 
> 
> Does the oops appear in the dmesg, too?
> 
> > This has got to be some kind of memory configuration issue. I've moved
> > the CS configuration for this device to different memory locations but
> > it doesn't change the behavior. I'm setting things up in U-Boot in
> > exactly the same way I had been setting them up in Colilo for the 2.6.10
> > kernel (where everything worked).
> > 

I agree, it sounds alot more like a deeper bug
than restricted to your video driver. I can't see
anything that would cause that (atleast yet). Would
be worth it to get some input from linux-m68k (coldfire m68k right?).

> 
> What about other memory mapped devices you might have on the system? Do
> they function properly? If not this might be indicator where look for
> the problem.
> 
> Regards,
> Hinko
> 
> -- 
> Hinko Kočevar, OSS developer
> ČETRTA POT, d.o.o.
> Planina 3, 4000 Kranj, SI EU
> tel     ++386 (0) 4 280 66 03
> e-mail  hinko.kocevar@cetrtapot.si
> http    www.cetrtapot.si
> 
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Linux-fbdev-devel mailing list
> Linux-fbdev-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel


-- 
Kristoffer Ericson <kristoffer.ericson@gmail.com>

[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[-- Attachment #3: Type: text/plain, Size: 182 bytes --]

_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel

  reply	other threads:[~2008-11-13 10:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11  1:54 Seg fault on any FB write (Epson S1D13A04 on Coldfire running 2.6.25) James Kimble
2008-11-11  9:57 ` Hinko Kocevar
2008-11-11 14:50   ` Seg fault on any FB write (Epson S1D13A04on " jkimble
2008-11-11 15:04     ` Hinko Kocevar
2008-11-11 16:10       ` Seg fault on any FB write (Epson S1D13A04onColdfire " jkimble
2008-11-12  8:25         ` Hinko Kocevar
2008-11-12 15:52           ` jkimble
2008-11-13  4:47           ` James Kimble
2008-11-13  8:50             ` Hinko Kocevar
2008-11-13 11:55               ` Kristoffer Ericson [this message]
2008-11-11 18:52       ` Seg fault on any FB write (Epson S1D13A04on Coldfire " Kristoffer Ericson
2008-11-11 18:02         ` Seg fault on any FB write (Epson S1D13A04onColdfire " jkimble
2008-11-11 19:14           ` Kristoffer Ericson
2008-11-11 18:20             ` jkimble
2008-11-11 19:29               ` Kristoffer Ericson
2008-11-12  8:34         ` Seg fault on any FB write (Epson S1D13A04on Coldfire " Hinko Kocevar
2008-11-11 15:06     ` jkimble
2008-11-11 18:50 ` Seg fault on any FB write (Epson S1D13A04 on " Kristoffer Ericson

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=20081113125502.0e43a930.kristoffer.ericson@gmail.com \
    --to=kristoffer.ericson@gmail.com \
    --cc=hinko.kocevar@cetrtapot.si \
    --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).