Date: Fri, 11 Nov 2005 12:09:50 -0800 (PST)
Message-Id: <20051111.120950.06356722.davem@davemloft.net>
To: agx@sigxcpu.org
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: sparc64: Oops in pci_alloc_consistent with cingergyT2
From: "David S. Miller" <davem@davemloft.net>
In-Reply-To: <20051111153354.GA19838@bogon.ms20.nix>
References: <20051111153354.GA19838@bogon.ms20.nix>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 987
Lines: 25

From: Guido Guenther <agx@sigxcpu.org>
Date: Fri, 11 Nov 2005 16:33:55 +0100

> This is due to the fact that cinergyt2_alloc_stream_urbs calls
> pci_alloc_consistent with a NULL argument for the pci dev (it's a USB
> device):
> 
> cinergyt2->streambuf = pci_alloc_consistent(NULL,
>                                               STREAM_URB_COUNT*STREAM_BUF_SIZE,
>                                               &cinergyt2->streambuf_dmahandle);
> 
> dma_alloc_coherent doesn't seem to be implemented on sparc64, what would
> be the right way to tackle this?

It should be using "usb_buffer_alloc()" or similar.

No USB driver should be calling the DMA mapping interfaces
directly.

Where is this driver?  I can't find it in the 2.6.x sources.
-
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/