public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@metabyte.com>
To: proski@gnu.org (Pavel Roskin)
Cc: linux-kernel@vger.kernel.org, perex@suse.cz (Jaroslav Kysela),
	zaitcev@metabyte.com (Pete Zaitcev),
	peter@cadcamlab.org, kai@thphy.uni-duesseldorf.de
Subject: Re: YMF PCI - thanks, glitches, patches (fwd)
Date: Wed, 6 Dec 2000 11:02:52 -0800 (PST)	[thread overview]
Message-ID: <200012061902.LAA21377@ns1.metabyte.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0012061254420.1411-100010@fonzie.nine.com> from "Pavel Roskin" at Dec 06, 2000 01:12:13 PM

> Date: Wed, 6 Dec 2000 13:12:13 -0500 (EST)
> From: Pavel Roskin <proski@gnu.org>
> cc: Jaroslav Kysela <perex@suse.cz>, Pete Zaitcev <zaitcev@metabyte.com>,
>         <peter@cadcamlab.org>, <kai@thphy.uni-duesseldorf.de>

> The native YMF PCI driver from Linux-2.4.0-test12-pre5 works on my card:

I did not have a chance to look at whatever is in 2.4, but from
reading Linus's e-mails I understand that Jaroslav made a new
port, which is probably unrelated to the stuff that I hastily
cooked up for 2.2 (I really wanted to play Doom on my new Sony).
I am sorry for the lack of communication.

I'll see what 2.2 does about 1) playing at 5512 Hz, 2) compiling
as modules together (non-modules are made to be exclusive),
3) compiling if CONFIG_PCI is not enabled, 4) has Configure.help
update.

I am not sure what to do about CONFIG_EXPERIMENTAL.
My current plan is to discard "(EXPERIMENTAL)" and forget
about it until the next case.

Ioctl 0x5401 is a mystery. I do not know what it is
(looks like SNDCTL_TMR_TIMEBASE without uppper bits).

Please send fewer attachements to the lists. Your sound fragment
is very useful, but I'd prefer to have it sent separately to me
upon a request (in uuencode :).

BTW, Legacy driver (ymf_sb) uses PC/DMA or whatever the name is,
which requires the north bridge support and, sometimes, additional
connections on the motherboard. This is not reflected in _any_
kernel documentation. I have spent numerous hours trying to make
it work on my laptop until I understood that even though my
chipset supports PC/DMA, necessary connections are missing.
At first glance, it looked as if IRQ does not come.

-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-06 19:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-06 18:12 YMF PCI - thanks, glitches, patches (fwd) Pavel Roskin
2000-12-06 19:02 ` Pete Zaitcev [this message]
2000-12-06 20:00   ` Pavel Roskin
2000-12-06 20:59     ` Pavel Roskin
2000-12-06 23:12     ` Pete Zaitcev
2000-12-07 13:37 ` Alan Cox
2000-12-07 16:44   ` Pavel Roskin
2000-12-07 16:48     ` Alan Cox
2000-12-08  2:37     ` Peter Samuelson

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=200012061902.LAA21377@ns1.metabyte.com \
    --to=zaitcev@metabyte.com \
    --cc=kai@thphy.uni-duesseldorf.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    --cc=peter@cadcamlab.org \
    --cc=proski@gnu.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