public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andris Pavenis <pavenis@latnet.lv>
To: Juergen Sawinski <juergen.sawinski@mpimf-heidelberg.mpg.de>
Cc: Doug Ledford <dledford@redhat.com>,
	"linux-kernel@vger" <linux-kernel@vger.kernel.org>
Subject: Re: Linux-2.4.20-pre4-ac1: i810_audio broken
Date: Wed, 28 Aug 2002 16:22:30 +0300	[thread overview]
Message-ID: <200208281622.30303.pavenis@latnet.lv> (raw)
In-Reply-To: <1030539078.1454.8.camel@voyager>

On Wednesday 28 August 2002 15:51, Juergen Sawinski wrote:
> Can you drop in the old (working) source into the new tree and see if
> that works? If that works I'll try making a step by step patch series,
> to see what breaks it.

Today's tests were done in that way (I only replaced i810_audio.c,
removed i810_audio.o, run 'make modules' and 'make modules_install' and tested 
the results). As I wrote earlier it seems that Dough's patch (to 
2.4.20-pre1-ac2) broke driver

Andris

> On Wed, 2002-08-28 at 09:04, Andris Pavenis wrote:
> > Verified that sound is already broken with 2.4.20-pre1-ac2, but works
> > with i810_audio.c from 2.4.19-pre1-ac1. Commenting 2 above mentioned
> > lines out doesn't help

  reply	other threads:[~2002-08-28 13:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-27  9:53 Linux-2.4.20-pre4-ac1: i810_audio broken Andris Pavenis
2002-08-27 18:46 ` Doug Ledford
2002-08-28  0:21   ` Juergen Sawinski
2002-08-28  0:30     ` Juergen Sawinski
2002-08-28  7:04   ` Andris Pavenis
2002-08-28 12:51     ` Juergen Sawinski
2002-08-28 13:22       ` Andris Pavenis [this message]
2002-08-28 15:21         ` Doug Ledford
2002-08-28 15:47           ` Juergen Sawinski
2002-08-28 16:07             ` Doug Ledford
2002-08-28 15:59           ` Andris Pavenis
2002-08-28 16:12             ` Doug Ledford

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=200208281622.30303.pavenis@latnet.lv \
    --to=pavenis@latnet.lv \
    --cc=dledford@redhat.com \
    --cc=juergen.sawinski@mpimf-heidelberg.mpg.de \
    --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