public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sanka Piyaratna <cesanka@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: PCIe interface memory memory mapping issue
Date: Fri, 12 Jun 2009 05:23:46 -0700 (PDT)	[thread overview]
Message-ID: <233030.36441.qm@web31706.mail.mud.yahoo.com> (raw)


Hi,

I have developed a PCI express interface using Xilinx ML555 hardware module. I have implemented Linux kernel mode device drivers and everything works correctly as long as I am using the device within a computer with dual channel DDR arrangement. However, as soon as I pug this device into a core i7 or an older single channel DDR machine, the interface memory mapping does not work any more. As if the register map with in the device does no longer exsists. However, "lspci" utility provides correct information. I am not sure if this has anything to do with the number of DDR memory channels the motherboard has or why that would be a problem for PCI express device. However, this seem to be the common link between the machines that demonstrate this issue.

Could some one please let me know if you have ever experience this kind of problem before and/or any ideas to fix this problem?

Thank you very much,

Regards,

Sanka



      Need a Holiday? Win a $10,000 Holiday of your choice. Enter now.http://us.lrd.yahoo.com/_ylc=X3oDMTJxN2x2ZmNpBF9zAzIwMjM2MTY2MTMEdG1fZG1lY2gDVGV4dCBMaW5rBHRtX2xuawNVMTEwMzk3NwR0bV9uZXQDWWFob28hBHRtX3BvcwN0YWdsaW5lBHRtX3BwdHkDYXVueg--/SIG=14600t3ni/**http%3A//au.rd.yahoo.com/mail/tagline/creativeholidays/*http%3A//au.docs.yahoo.com/homepageset/%3Fp1=other%26p2=au%26p3=mailtagline

             reply	other threads:[~2009-06-12 12:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 12:23 Sanka Piyaratna [this message]
2009-06-13  5:50 ` PCIe interface memory memory mapping issue Robert Hancock
2009-06-14 12:43   ` Sanka Piyaratna
2009-06-14 16:26     ` Robert Hancock
2009-06-14 23:36       ` Sanka Piyaratna

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=233030.36441.qm@web31706.mail.mud.yahoo.com \
    --to=cesanka@yahoo.com \
    --cc=linux-kernel@vger.kernel.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