linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <shahamit@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Inconsistent accesses to SDRAM on a PCI card
Date: Thu, 26 Aug 2004 16:30:53 +0000	[thread overview]
Message-ID: <cgl2ht$sr0$1@sea.gmane.org> (raw)

Hi all,

Since there seems to be no list dedicated to Linux + PCI, I'll ask my
question here.

I have a custom board that has the Marvell 64360 bridge. It has a powerpc
750GX processor on it and 256MB of SDRAM.

I wrote a host driver that could access the RAM via a /dev interface (I'm
using kernel 2.6.6 on the host). I can read / write from the device to the
sdram on the board. I also have u-boot running on the board, so I can
read / write from / to SDRAM on the board via u-boot. Basically, I can dump
a Linux kernel to the board via the host PCI interface and jump to the
kernel on the board via u-boot.

This worked fine while I worked with this setup on an IBM pserver machine.
However, when I switched to a locally assembled machine based on the intel 
SE7210TP1-E [1] chipset, u-boot's and PCI's view of SDRAM on the board
changed completely.

If I dump the kernel to an offset of 5 MB on the board via the PCI
interface, u-boot doesn't see it. The contents before and after dumping the
kernel remain the same. Ditto over the PCI interface. If I do any writes
via u-boot to the SDRAM, the PCI can't see the newly written contents.

This is very strange, I couldn't find an answer anywhere in the BIOS
settings or any kernel settings. Since the kernel, u-boot, host tools, etc,
haven't changed, and it's just the machine that has changed, I'm guessing
it's the PCI interface or the BIOS initializations that are causing some
funny things to happen.

Any clue why this should be happening?

Thanks,
Amit.


[1] http://www.intel.com/design/servers/boards/SE7210TP1-E/

-- 
Amit Shah
http://amitshah.nav.to/



-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2004-08-26 16:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 16:30 Amit Shah [this message]
2004-08-26 16:48 ` Inconsistent accesses to SDRAM on a PCI card Greg KH
2004-08-26 17:26 ` Amit Shah
2004-08-26 22:56 ` Sabharwal, Atul

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='cgl2ht$sr0$1@sea.gmane.org' \
    --to=shahamit@gmail.com \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).