linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "R. Ebersole (VTI - new)" <rje@valleytech.com>
To: David Hawkins <dwh@ovro.caltech.edu>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: mmap + segfaults on MPC8349E
Date: Sat, 15 Dec 2007 01:40:26 -0500	[thread overview]
Message-ID: <476376DA.9010608@valleytech.com> (raw)
In-Reply-To: <475DF30A.1080202@ovro.caltech.edu>

[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]


Dave,

Attached is the driver code that was in use when we had the problem.
(FPGA_orig.7z)

We think that we *may* have resolved the issue.
We have not, yet, completed testing the resolution, however.

Attached is the updated version of the driver (FPGArw.7z).
So far, this version appears OK when using mmap() without
MAP_FIXED.  We open() the device O_RDWR | O_SYNC.

We were going to switch to using pread(), pwrite(), and ioctl() to
access the FPGA's registers, but we are going to hold off on that
for now.



David Hawkins wrote:

> Hi,
>
> Ok, so assuming you come back with the fact that the seg-fault
> occurs without bursting. Lets take a look at your driver code.
>
> Cheers,
> Dave
>
>
>

-- 

Sometimes I feel like a red shirt in the Star Trek episode of life.

--

This message contains confidential information and is intended only for the
individual named.  If you are not the intended recipient you should not
disseminate, distribute or copy this e-mail.  Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and delete
this e-mail from your system.


[-- Attachment #2: FPGArw.7z --]
[-- Type: application/octet-stream, Size: 3775 bytes --]

[-- Attachment #3: FPGA_orig.7z --]
[-- Type: application/octet-stream, Size: 2544 bytes --]

  reply	other threads:[~2007-12-15  6:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-09  2:44 mmap + segfaults on MPC8349E R. Ebersole (VTI - new)
2007-12-09  4:01 ` David Hawkins
2007-12-11  1:53   ` R. Ebersole (VTI - new)
2007-12-11  2:16     ` David Hawkins
2007-12-15  6:40       ` R. Ebersole (VTI - new) [this message]
2007-12-15 19:55         ` David Hawkins

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=476376DA.9010608@valleytech.com \
    --to=rje@valleytech.com \
    --cc=dwh@ovro.caltech.edu \
    --cc=linuxppc-embedded@ozlabs.org \
    /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).