mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Samuli Suonpaa <suonpaa@iki.fi>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.13-acX: NM256 hangs at boot
Date: Mon, 29 Oct 2001 06:16:23 -0500	[thread overview]
Message-ID: <3BDD3A87.B98104B0@mandrakesoft.com> (raw)
In-Reply-To: <E15yAHE-0002M1-00@the-village.bc.nu>

Alan Cox wrote:
> > NM256 is PCI-based, so I checked whether CONFIG_HOTPLUG_PCI would have
> > any effect. It didn't.
> >
> > Exactly the same thing happens with 2.4.13-ac4.
> >
> > If I compile the kernel without sound-support, everything works just
> > fine.
> 
> Jeff Garzik updated the neomagic driver to use the generic ac97 codec. It
> looks like he didnt quite get it right firs ttime around. I'll take a look
> and its then a case of either fixing it or reverting Jeff's change

If you don't see something right off, go ahead and revert it.

IIRC now, nm256 had trouble with completely locking the PCI bus if you
touched the wrong AC97 registers.  The solution was to create
ac97_codec_{read,write} that filtered register numbers depending on a
codec-specific mask, thus avoiding those registers on nm256 and using
them on other chips.  This change isn't in anybody's ac97_codec (except
an old CVS of mine), and it was never fully debugged when I had a hands
on a laptop with [supposed] ac97 codec nm256 on it.

So, I am hoping it's a stupid error like "using ac97 mixer when I
shouldn't", otherwise it's likely too much trouble to bother with.

-- 
Jeff Garzik      | Only so many songs can be sung
Building 1024    | with two lips, two lungs, and one tongue.
MandrakeSoft     |         - nomeansno


  reply	other threads:[~2001-10-29 11:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-29 10:41 Samuli Suonpaa
2001-10-29 10:52 ` Jeff Garzik
2001-10-29 11:36   ` Samuli Suonpaa
2001-10-29 11:08 ` Alan Cox
2001-10-29 11:16   ` Jeff Garzik [this message]
2001-10-29 11:33     ` 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=3BDD3A87.B98104B0@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suonpaa@iki.fi \
    /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®