linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Kimble <jkimble@one.net>
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: Wed, 12 Nov 2008 23:47:32 -0500	[thread overview]
Message-ID: <491BB164.2020203@one.net> (raw)
In-Reply-To: <491A930F.2040507@cetrtapot.si>


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?

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 
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.

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'm really stuck. If anyone has any ideas or suggestions I'd really 
appreciate your thoughts.

Thanks for your attention...


Hinko Kocevar wrote:
> jkimble@one.net wrote:
>   
>> I thought it looked OK because it looks the same as the flexCAN stuff.
>> However I just noticed that flexCAN has a .0 and .1 whereas the s1d13 are
>> both .0. Yeah, I hope an expert weighs in on this because I'm not sure
>> now.
>>
>> I didn't get your attachement.
>>
>>     
>
> Maybe I forgot to attach it :P
> Here it is.
>
>
> HTH,
> HK
>
>
>   


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

  parent reply	other threads:[~2008-11-13  4:47 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 [this message]
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=491BB164.2020203@one.net \
    --to=jkimble@one.net \
    --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).