All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Kimble <jkimble@one.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Seg fault on any FB write (Epson S1D13A04 on Coldfire running 2.6.25)
Date: Mon, 10 Nov 2008 20:54:11 -0500	[thread overview]
Message-ID: <4918E5C3.2090108@one.net> (raw)


I've been working on porting the s1d13xxxfb driver from the latest 
kernel from Freescale for Coldfire to work with the S1D13A04 chip. I was 
able to get things working to the point that I do get a little TUX logo 
up on the screen at boot up. Seemed like a good start but none of my 
user space applications will work. I can open the /dev/fb0 device and 
the data in the info structure is correct but if I try to write to any 
register or area in the frame buffer (or write to the device at all) I 
get a seg fault.

I had an earlier driver working with the 2.6.10 kernel with the same 
hardware. The same application space program should work ( I would 
think...) but I get the seg fault on the first write to fb0. I tried a 
different memory location (ox4400 0000 to 0x7400 0000) for the CS 
associated with the video  chip, no  difference. Permissions for 
/dev/fb0 are "rw". No other process using fb0. This is really weird.

Any help or suggestions MUCH appreciated.

-------------------------------------------------------------------------
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=/

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

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11  1:54 James Kimble [this message]
2008-11-11  9:57 ` Seg fault on any FB write (Epson S1D13A04 on Coldfire running 2.6.25) 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
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=4918E5C3.2090108@one.net \
    --to=jkimble@one.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.