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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 20 Jun 2008 21:45:16 +0200
From:	Pierre Ossman <drzeus@...eus.cx>
To:	Takashi Iwai <tiwai@...e.de>, Jaroslav Kysela <perex@...ex.cz>
Cc:	Rene Herman <rene.herman@...access.nl>,
	ALSA devel <alsa-devel@...a-project.org>, mulix@...ix.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [alsa-devel] looping S/PDIF data

On Thu, 19 Jun 2008 14:48:19 +0200
Takashi Iwai <tiwai@...e.de> wrote:

> At Thu, 19 Jun 2008 14:39:05 +0200 (CEST),
> Jaroslav Kysela wrote:
> > 
> > I don't think that this patch is correct. DMA transfers should be disabled 
> > by:
> > 
> > outl(what, TRID_REG(trident, T4D_STOP_B));
> > outl(val, TRID_REG(trident, T4D_AINTEN_B));
> 
> They are already in the trigger callback as long as I saw the code
> quickly.  So the problem should be somewhere else.
> 
> > lines. Adding &= ~SPDIF_EN can disable output from AC97 to S/PDIF as well.
> 
> That's true.
> 
> Anyway, if you are up now, I'll let you hunt further as you are the
> author of the driver :)
> 

Are there any specs on this hardware? I could play around a bit myself,
but I can't really find any documentation on the registers.

Rgds
-- 
     -- Pierre Ossman

  WARNING: This correspondence is being monitored by the
  Swedish government. Use end-to-end encryption where
  possible.

Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ