From: "Thomas Munck Steenholdt" <tmus@get2net.dk>
To: dledford@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: i810 sound broken...
Date: Thu, 8 Aug 2002 10:37:38 +0200 [thread overview]
Message-ID: <200208080837.g788bcM01508@eday-fe6.tele2.ee> (raw)
> On Mon, Aug 05, 2002 at 08:38:52PM +0200, Thomas Munck Steenholdt wrote:
> > On Mon, 2002-08-05 at 17:28, Alan Cox wrote:
> > > On Mon, 2002-08-05 at 14:47, venom@sns.it wrote:
> > > > Still OSS modules for i810 does not work with 2.5 kernels, actually 2.4
> > > > is fine. No time to switch to alsa (and not interested for now too).
> > >
> > > OSS for 2.5 is someone elses problem. I have no plan to do any work on
> > > the old OSS drivers for the 2.5 tree or even to submit 2.4 updates into
> > > 2.5 for it.
> > >
> >
> > So anyway - How should I go about determining the exact problem on my
> > box... I've had it all along, and I know for a fact that the hardware is
> > OK... Modules are loaded correctly, but it just does not work!
>
> I'll tell you what you can do. Grab some ICH docs so you have a list of
> the valid regs on the i810 sound chip. Then, go into i810_audio.c and
> write me up a little hack that, at the end of the chip init sequence,
> whill dump the state of all the regs on the chip. Make it smart enough to
> know about different regs on different chips (aka, Intel ICH0 and ICH1
> will probably have a slightly different reg setup than the ICH2 and
> later). Then, load that driver on your machine and get me that register
> dump. Then, I'll take the patch and apply it here on the i810 machines I
> have that do work and get their register dump. We'll see then where the
> differences are. On the i845 based machine I have at work, where the
> sound doesn't work just like you describe, I've isolated the problem down
> to the fact that when we start the DMA engine it *immediately* signals
> that it has already finished the DMA process and has already stopped again
> but it never actually does the DMA. So, I suspect there is some config
> bit somewhere set wrong and the DMA is not taking place as a result (hell,
> for all I know, the AC97 link for sound output may be off or something
> like that). Getting a register dump from several busted machines as well
> as from some working machines should enable me to solve the problem
> relatively easily. I just haven't had the time to write the patch myself
> and do any more work on the thing :-(
Please excuse me for not immediately responding with a working hack for this.
I'm sorry to say that I have not yet had any experience in kernel programming
and even though I jumped on the "job" as soon as I saw you mail, I quickly
realized that I probably need some time of practicing, figuring out how stuff
is done, and get into the actual close-to-hardware programming that is
required for stuff like this...
Instead of promising to have a hack ready at any time... I'll follow this
case closely and see what I can learn from it. I need to get
into how stuff is done in this kind of area.
Hopefully some day you'll see meactually post a patch of some
kind... ;-)
Back to the case... I realized that I might not have explained myself
correctly regarding my hardware...
My machine is i845 based, using the i810 driver for audio...
it is not i810 based!
Thomas
-- Send gratis SMS og brug gratis e-mail på Everyday.com --
next reply other threads:[~2002-08-08 8:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 8:37 Thomas Munck Steenholdt [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-06 7:24 Andris Pavenis
2002-08-05 11:27 Thomas Munck Steenholdt
2002-08-05 12:54 ` Alan Cox
2002-08-05 13:47 ` venom
2002-08-05 15:28 ` Alan Cox
2002-08-05 18:38 ` Thomas Munck Steenholdt
2002-08-06 0:26 ` Jeff Chua
2002-08-07 15:05 ` Doug Ledford
2002-08-07 18:49 ` Juergen Sawinski
2002-08-08 20:47 ` Doug Ledford
2002-08-05 21:38 ` Alexander Hoogerhuis
2002-08-06 14:47 ` Alan Cox
2002-08-06 13:31 ` Alexander Hoogerhuis
2002-08-05 20:21 ` Juergen Sawinski
2002-08-05 21:44 ` Alan Cox
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=200208080837.g788bcM01508@eday-fe6.tele2.ee \
--to=tmus@get2net.dk \
--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®