From: Andris Pavenis <pavenis@latnet.lv>
To: Doug Ledford <dledford@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux-2.4.20-pre4-ac1: i810_audio broken
Date: Wed, 28 Aug 2002 10:04:07 +0300 [thread overview]
Message-ID: <200208281004.07891.pavenis@latnet.lv> (raw)
In-Reply-To: <20020827144629.E28828@redhat.com>
On Tuesday 27 August 2002 21:46, Doug Ledford wrote:
> On Tue, Aug 27, 2002 at 12:53:12PM +0300, Andris Pavenis wrote:
> > Found that i810_audio has been broken in kernel 2.4.20-pre4-ac1. It was
> > Ok with 2.4.20-pre1-ac1 I used before.
> >
> > With 2.4.20-pre4-ac1 I'm only getting garbled sound and kernel messages
> > (see below). Didn't have time yet to study mire detailed which change
> > breaks driver.
>
> The important part of my change is just two lines. There is the line that
> prints out the message "Defaulting to base 2 channel mode." and the line
> after it where we mask off a couple bits in the global control register.
> Comment those two lines out and let me know if it makes a difference on
> your machine.
>
> > In Alan's changelog I see:
> >
> > 2.4.20-pre2-ac5: Further i810_audio updates for 845 (Juergen Sawinski)
> > 2.4.20-pre1-ac3: Tidy up error paths on i810_audio init (Alan)
> > 2.4.20-pre1-ac2: First set of i810 audio updates (Doug Ledford)
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
Andris
next prev parent reply other threads:[~2002-08-28 7:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-27 9:53 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 [this message]
2002-08-28 12:51 ` Juergen Sawinski
2002-08-28 13:22 ` Andris Pavenis
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=200208281004.07891.pavenis@latnet.lv \
--to=pavenis@latnet.lv \
--cc=dledford@redhat.com \
--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
all inboxes | Powered by JetHome®