From: Pete Zaitcev <zaitcev@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"M.H.VanLeeuwen" <vanl@megsinet.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ymf724 oops in 2.4.22, boot fails
Date: Tue, 2 Sep 2003 13:14:22 -0400 [thread overview]
Message-ID: <20030902131422.B14511@devserv.devel.redhat.com> (raw)
In-Reply-To: <200309021707.h82H7I628954@devserv.devel.redhat.com>; from vanl@megsinet.net on Fri, Aug 29, 2003 at 03:45:44PM -0500
> a. if the read of AC97_EXTENDED_ID fails just leave eid NULL and continue
> to fix??? no codec attached. Here is my dmesg output for this device:
Alan, don't forget to double-check cs46xx. All the code
in ymfpci which handles ac97 is taken from there.
I don't think 2.4 at this stage is a good place for
bulk renamings like codec=>unit.
-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
> a. if the read of AC97_EXTENDED_ID fails just leave eid NULL and continue
> to fix??? no codec attached. Here is my dmesg output for this device:
Alan, don't forget to double-check cs46xx. All the code
in ymfpci which handles ac97 is taken from there.
I don't think 2.4 at this stage is a good place for
bulk renamings like codec=>unit.
-- Pete
next parent reply other threads:[~2003-09-02 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200309021707.h82H7I628954@devserv.devel.redhat.com>
2003-09-02 17:14 ` Pete Zaitcev [this message]
2003-08-29 20:45 [PATCH] ymf724 oops in 2.4.22, boot fails M.H.VanLeeuwen
2003-08-29 20:48 ` M.H.VanLeeuwen
2003-08-29 23:20 ` 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=20030902131422.B14511@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=vanl@megsinet.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.