To: Manu Abraham <abraham.manu@gmail.com>
Cc: Greg KH <greg@kroah.com>, linux-pci@atrey.karlin.mff.cuni.cz,
       linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PCIE
References: <46543045.3030904@gmail.com> <20070523155958.GA5282@kroah.com>
	<4654AB40.6060208@gmail.com> <adaejl79rh0.fsf@cisco.com>
	<4654BC10.2000808@gmail.com>
From: Roland Dreier <rdreier@cisco.com>
Date: Wed, 23 May 2007 15:23:40 -0700
In-Reply-To: <4654BC10.2000808@gmail.com> (Manu Abraham's message of "Thu, 24 May 2007 02:11:28 +0400")
Message-ID: <adazm3v89hv.fsf@cisco.com>
User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.19 (linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 831
Lines: 22

 > If i uncomment the saa716x_read or write, what i get is a solid freeze
 > on module load. If i leave it commented out, the module loads fine.

That sounds like a typical bug during driver development... you're
probably wedging the hardware by doing the wrong access.

I didn't see the source for saa716x_read or write in the code you
posted, so it's hard to say if there's a problem with them.

Is your interrupt handler getting called?  Is the device generating
interrupts?

 > That part is then fine. Does MSI require any special tinkering ?

Just pci_enable_msi() as usual.

 - R.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/