linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
To: jkimble@one.net
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Seg fault on any FB write (Epson S1D13A04on Coldfire running 2.6.25)
Date: Tue, 11 Nov 2008 16:04:03 +0100	[thread overview]
Message-ID: <49199EE3.5090101@cetrtapot.si> (raw)
In-Reply-To: <43185.137.237.242.42.1226415047.squirrel@webmail.nuvox.net>

jkimble@one.net wrote:
>> James Kimble wrote:
> 
> /proc/iomem shows:
> 
> 74000000-74009000 : s1d13a04fb.0
> 74000000-74009000 : s1d13xxxfb regs
> 74040000-74068000 : s1d13a04fb.0
> 74040000-74068000 : s1d13xxxfb mem

I'm not sure if this is correct - two drivers mapped the same region twice !?
Maybe the experts will shed some light on this..

> f000070c-f000070c : spi-int-mask
> f0000740-f000075f : spi-int-level
> f0000a50-f0000a50 : spi-par
> f0008a00-f0008ab8 : spi-module
> f0008f00-f0008f20 : MCF548X-i2c
> f000a000-f000a7ff : mcf548x-flexcan.0
> f000a000-f000a7ff : mcf548x-flexcan
> f000a800-f000afff : mcf548x-flexcan.1
> f000a800-f000afff : mcf548x-flexcan
> f0020000-f0033000 : fsl-sec1
> fc000000-ffffffff : physmap-flash.0
> 

I haven't took a long look at your driver, but here is our driver for S13706FB that
we use on our embedded platform. Hope it helps.

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

  reply	other threads:[~2008-11-11 15:07 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 [this message]
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=49199EE3.5090101@cetrtapot.si \
    --to=hinko.kocevar@cetrtapot.si \
    --cc=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 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).