lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 08 Feb 2012 09:30:40 +0100 From: Takashi Iwai <tiwai@...e.de> To: "Heasley, Seth" <seth.heasley@...el.com> Cc: David Henningsson <david.henningsson@...onical.com>, "alsa-devel@...a-project.org" <alsa-devel@...a-project.org>, "perex@...ex.cz" <perex@...ex.cz>, "Ralston, James D" <james.d.ralston@...el.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [alsa-devel] [PATCH 1/6] hda_intel: Add Lynx Point HD Audio Controller DeviceIDs At Wed, 8 Feb 2012 00:35:33 +0000, Heasley, Seth wrote: > > >> I'm also in favor of not rocking the boat, but I'm curious what > >changing this would entail, and what would be the advantage or rationale > >for making the change? > > > >Reading the LPIB register, and reading the DMA position buffer, are two > >different methods of reading the current playback (or recording) > >position, i e which sample is currently being played back. > > > >The problem is that some chipsets prefer one method over the other, i e, > >only one of the methods work reliably. And if the other method only > >breaks occasionally, this can be quite difficult to detect and track > >down - we will have users complaining about their audio sometimes either > >sounding distorted, maybe not working at all, or just once in a while > >glitches. All of these symptoms can have many causes, so deducing that > >to a broken playback position is time consuming. That's why I think it's > >worth the extra question, to get it right from the start. > > > >So...thanks in advance for looking it up for us? :-) > > I'm inquiring about it, but I can say that it seems to work just fine using the DMA position buffer. OK, I merged the patch now as is. Please let me know if you find a problem. thanks, Takashi -- 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