Date: Fri, 11 Nov 2005 12:13:27 -0800 (PST)
Message-Id: <20051111.121327.57756233.davem@davemloft.net>
To: alan@lxorguk.ukuu.org.uk
Cc: agx@sigxcpu.org, linux-kernel@vger.kernel.org
Subject: Re: sparc64: Oops in pci_alloc_consistent with cingergyT2
From: "David S. Miller" <davem@davemloft.net>
In-Reply-To: <1131738080.3174.33.camel@localhost.localdomain>
References: <20051111153354.GA19838@bogon.ms20.nix>
	<1131738080.3174.33.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 693
Lines: 15

From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Date: Fri, 11 Nov 2005 19:41:20 +0000

> The DMA channel in question is the PCI hub to which the device is
> connected. So it should not be using NULL, it should be passing the pci
> device id of the bus controller to whom it is attached

We have USB buffer allocation routines for drivers which abstract this
away and perform all the calls correctly, so none of this knowledge
needs to be in a USB driver.
-
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/