From: Tony Nugent <tony@growzone.com.au>
To: linux-sound@vger.kernel.org
Subject: Re: next to last maestro update? (fwd)
Date: Sat, 30 Oct 1999 03:07:21 +0000 [thread overview]
Message-ID: <marc-linux-sound-94125689721967@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-94122443129261@msgid-missing>
On Fri Oct 29 1999 at 11:02, Zach Brown wrote:
> oh my goodness guys, I'm such a dork for not sending this your way...
Gnah! You sure are!
> ---------- Forwarded message ----------
> From: Zach Brown <zab@redhat.com>
> Subject: next to last maestro update?
> v0.10 of the OSS maestro driver is on http://people.redhat.com/zab/maestro
>
> it finally fixes the memory scribbling, I hope. It also has some minor
> fixes that made it work on some laptops. Please do give this one a spin,
> it should be stable.
>
> the next hurdle is to fix up the proper LRLR support so that mmap() (read:
> quake) works :)
Quake? Really?
Oh man, I'm running a box with dual p-iii550/256Mb ram here, with a
banshee card in it (soon to be replaced by a 3500 voodoo3), and a
PCI128 (es1371) sound card.
The quake3 demo runs like total crap on this box, only to discover
that the current demo version doesn't like PCI-based sound cards.
Major bummer :-(
(I've seen the q3 demo scream on a p450 with a 32Mb TNT, but those
boxes had an onboard crystal sound chip. Very impressive).
Does this mean that a fix is on the way so that I'll finally be able
to have some fun running q3 on this box with the pci sound card?
Cheers
Tony
next prev parent reply other threads:[~1999-10-30 3:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-29 15:02 next to last maestro update? (fwd) Zach Brown
1999-10-30 3:07 ` Tony Nugent [this message]
1999-10-30 14:27 ` Zach Brown
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=marc-linux-sound-94125689721967@msgid-missing \
--to=tony@growzone.com.au \
--cc=linux-sound@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