[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1005071048220.1804-100000@iolanthe.rowland.org>
Date: Fri, 7 May 2010 10:51:10 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: Daniel Mack <daniel@...aq.de>
cc: Clemens Ladisch <clemens@...isch.de>, Takashi Iwai <tiwai@...e.de>,
<alsa-devel@...a-project.org>, Greg KH <gregkh@...e.de>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
USB list <linux-usb@...r.kernel.org>,
Kernel development list <linux-kernel@...r.kernel.org>,
Chris Wright <chrisw@...s-sol.org>,
<iommu@...ts.linux-foundation.org>,
Andi Kleen <andi@...stfloor.org>,
Pedro Ribeiro <pedrib@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
David Woodhouse <dwmw2@...radead.org>
Subject: Re: [alsa-devel] USB transfer_buffer allocations on 64bit systems
On Fri, 7 May 2010, Daniel Mack wrote:
> > At least the audio class and ua101 drivers don't do this and fill the
> > buffers before they are submitted.
>
> Gnaa, you're right. I _thought_ my code does it the way I described, but
> what I wrote is how I _wanted_ to do it, not how it's currently done. I
> have a plan to change this in the future.
>
> So unfortunately, that doesn't explain it either. Sorry for the noise.
At one point we tried an experiment, printing out the buffer and DMA
addresses. I don't recall seeing anything obviously wrong, but if an
IOMMU was in use then that might not mean anything. Is it possible
that the IOMMU mappings sometimes get messed up for addresses above 4
GB?
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists