From: "John W. Linville" <linville@tuxdriver.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch 2.4.29] i810_audio: offset LVI from CIV to avoid stalled start
Date: Sun, 23 Jan 2005 09:48:59 -0500 [thread overview]
Message-ID: <20050123144856.GA28932@tuxdriver.com> (raw)
In-Reply-To: <20050122030258.GA776@gondor.apana.org.au>
On Sat, Jan 22, 2005 at 02:02:58PM +1100, Herbert Xu wrote:
> On Fri, Jan 21, 2005 at 09:07:13AM +1100, herbert wrote:
> > On Thu, Jan 20, 2005 at 05:01:21PM -0500, John W. Linville wrote:
> > > On Thu, Jan 20, 2005 at 04:23:46PM -0500, John W. Linville wrote:
> > > > + * the next sg segment, it won't even get a start. So, instead, when
> > > > + * we are stopped, we increment the CIV value to the next sg segment
> > > > + * to be played so that when we call start, things will operate
> > > > + * properly
> > > > + */
> OK I dug into the archives and found that the reason we need to do
> it this way is because you can't set the value of CIV directly. So
> how about s/CIV/LVI/ in the last sentence?
Herbert,
Agreed...I will post a patch to that effect shortly...
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2005-01-23 14:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 20:22 [patch 2.4.29] i810_audio: offset LVI from CIV to avoid stalled start John W. Linville
2005-01-20 20:27 ` Herbert Xu
2005-01-20 21:07 ` John W. Linville
2005-01-20 21:23 ` John W. Linville
2005-01-20 22:01 ` John W. Linville
2005-01-20 22:07 ` Herbert Xu
2005-01-22 3:02 ` Herbert Xu
2005-01-23 14:48 ` John W. Linville [this message]
2005-01-23 14:54 ` John W. Linville
2005-08-03 18:18 ` [patch 2.4.32-pre1] " John W. Linville
2005-08-03 18:35 ` John W. Linville
2005-08-03 18:36 ` [patch 2.4.32-pre1 (corrected)] " John W. Linville
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050123144856.GA28932@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox