Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750786AbVL2QDW (ORCPT ); Thu, 29 Dec 2005 11:03:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750787AbVL2QDW (ORCPT ); Thu, 29 Dec 2005 11:03:22 -0500 Received: from fmmailgate04.web.de ([217.72.192.242]:17089 "EHLO fmmailgate04.web.de") by vger.kernel.org with ESMTP id S1750786AbVL2QDW convert rfc822-to-8bit (ORCPT ); Thu, 29 Dec 2005 11:03:22 -0500 Date: Thu, 29 Dec 2005 17:03:12 +0100 Message-Id: <395603262@web.de> MIME-Version: 1.0 From: =?iso-8859-1?Q?Burkhard=20Sch=F6lpen?= To: PaulFulghum Cc: linux-kernel@vger.kernel.org Subject: Re: PCI DMA burst delay Organization: http://freemail.web.de/ Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1358 Lines: 33 >Paul Fulghum schrieb am 29.12.05 16:30:20: > >Burkhard Sch?lpen wrote: >> ... in the (rarely) faulty case, the 2nd burst only starts >> after another delay of about 600ns, which is too late > >Looking at the PCI 2.3 specification, >arbitration latency on the order of a microsecond >or two does not seem excessive for a 33MHz bus. Okay, then I think I have to figure out, why I cannot get longer bursts than 512 Bits...does anybody have a clue how I can handle that? >> ... I deactivated all other pci devices that could disturb the transfers? > >Are you accessing registers on your device >during the DMA transfers? If so, the CPU is >acting as a PCI master that could delay granting >the bus to your device. No, I just made sure that not. There are no register accesses during dma transfer. The driver sends the application to sleep until an interrupt signals the completeness. Kind regards, Burkhard ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 - 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/