Re: status of 'device awe' ?
On Tue, Feb 22, 2000 at 04:10:02PM -0800, Andy Sparrow wrote: AFAIK, the AWE cannot work without this, and the cards PnPinfo seems to not include the other two registers - and if you don't probe them, then the 'awe' driver check doesn't see the EMU8000... Is there even a single person out there able to use the AWE device under Voxware in -current? No, but that's sort of moot as far as I'm concerned, since I also can't record sound (see "Creative SB AWE64 recording does not work" on freebsd-current). It comes out as static regardless of the input source. There are just so many things broken right now, I haven't got time to worry about not having sound recording, but it'll be sad if 4.0 is released in this state. -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of 'device awe' ?
On Tue, Feb 22, 2000 at 23:33:26 +0100, Jeroen Ruigrok van der Werven wrote: -On [2222 23:25], Daniel O'Connor ([EMAIL PROTECTED]) wrote: On 22-Feb-00 Jeroen Ruigrok van der Werven wrote: Should be used instead. I am so in favor of just declaring voxware dead... But the armchair generals wouldn't like that. The awe device controls the AWE's wavetable.. newpcm doesn't talk to this (yet - no idea if there are any plans) newmidi is underway... That's why I wanted to kill voxware in 4.0, would allow pcm to be used from default... Now we're stuck to the voxware crap for another release cycle until 5.0 hits the public. Voxware may be "crap", but newpcm doesn't work right for my GUS PnP. (And yep, I sent mail to the multimedia list, which got some response, and I sent mail to Cameron, which got no response.) Voxware used to work fine, way back when. Luigi's pcm code worked fine as well with my GUS PnP. Maybe it's time for me to switch back to voxware from newpcm. I'm tired of getting static every once in a while when playing sound files. I don't see any reason to get rid of voxware before newpcm is fully functional. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of 'device awe' ?
On Tue, 22 Feb 2000 16:10:02 -0800, Andy Sparrow [EMAIL PROTECTED] said: Andy Unfortunately for those of us who used to use 'pnp' commands in Andy userconfig to probe/init the AWE registers, the AWE wavetable is Andy already useless in -current. Andy AFAIK, the AWE cannot work without this, and the cards PnPinfo Andy seems to not include the other two registers - and if you don't Andy probe them, then the 'awe' driver check doesn't see the EMU8000... My newmidi patch includes a quirk to add the extra IO ports missing in the pnp information provided by EMU8000. That part of the patch is extracted into: http://people.FreeBSD.org/~tanimura/patches/awequirk.diff although not sure if the old-fashioned awe driver makes use of it... -- Seigo Tanimura [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of 'device awe' ?
-On [2221 21:15], Lyndon Nerenberg ([EMAIL PROTECTED]) wrote: LINT has an entry for an 'awe' device, however there doesn't appear to be any corresponding source code in the tree. Is this device dead? If so, the entry should be removed from LINT, or an appropriate comment added. device pcm device sbc Should be used instead. I am so in favor of just declaring voxware dead... But the armchair generals wouldn't like that. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of 'device awe' ?
On 22-Feb-00 Jeroen Ruigrok van der Werven wrote: Should be used instead. I am so in favor of just declaring voxware dead... But the armchair generals wouldn't like that. The awe device controls the AWE's wavetable.. newpcm doesn't talk to this (yet - no idea if there are any plans) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of 'device awe' ?
-On [2222 23:25], Daniel O'Connor ([EMAIL PROTECTED]) wrote: On 22-Feb-00 Jeroen Ruigrok van der Werven wrote: Should be used instead. I am so in favor of just declaring voxware dead... But the armchair generals wouldn't like that. The awe device controls the AWE's wavetable.. newpcm doesn't talk to this (yet - no idea if there are any plans) newmidi is underway... That's why I wanted to kill voxware in 4.0, would allow pcm to be used from default... Now we're stuck to the voxware crap for another release cycle until 5.0 hits the public. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of 'device awe' ?
On 22-Feb-00 Jeroen Ruigrok van der Werven wrote: That's why I wanted to kill voxware in 4.0, would allow pcm to be used from default... Now we're stuck to the voxware crap for another release cycle until 5.0 hits the public. shrugs You don't _have_ to use it :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of 'device awe' ?
On Tue, Feb 22, 2000 at 03:46:04PM -0700, Kenneth D. Merry wrote: On Tue, Feb 22, 2000 at 23:33:26 +0100, Jeroen Ruigrok van der Werven wrote: -On [2222 23:25], Daniel O'Connor ([EMAIL PROTECTED]) wrote: On 22-Feb-00 Jeroen Ruigrok van der Werven wrote: Should be used instead. I am so in favor of just declaring voxware dead... But the armchair generals wouldn't like that. The awe device controls the AWE's wavetable.. newpcm doesn't talk to this (yet - no idea if there are any plans) newmidi is underway... That's why I wanted to kill voxware in 4.0, would allow pcm to be used from default... Now we're stuck to the voxware crap for another release cycle until 5.0 hits the public. Voxware may be "crap", but newpcm doesn't work right for my GUS PnP. (And yep, I sent mail to the multimedia list, which got some response, and I sent mail to Cameron, which got no response.) Voxware used to work fine, way back when. Luigi's pcm code worked fine as well with my GUS PnP. Maybe it's time for me to switch back to voxware from newpcm. I'm tired of getting static every once in a while when playing sound files. I don't see any reason to get rid of voxware before newpcm is fully functional. Unfortunately for those of us who used to use 'pnp' commands in userconfig to probe/init the AWE registers, the AWE wavetable is already useless in -current. AFAIK, the AWE cannot work without this, and the cards PnPinfo seems to not include the other two registers - and if you don't probe them, then the 'awe' driver check doesn't see the EMU8000... Is there even a single person out there able to use the AWE device under Voxware in -current? My understanding is that this is no longer possible, following the removal of the 'pnp' interface in userconfig.. So, people with the AWE32, AWE daughter card or the AWE64 might as well have an original SoundBlaster 16, for all the good the EMU8000 wavetable/synth chip does them. If that is really so, then I would suggest that either: a) the 'awe' driver is now just so much cruft and should be removed. or b) FreeBSD has lost significant functionality (namely, AWE wavetable support) with the removal of the older 'pnp' interface, and this should be put back. I guess that your perspective on this really depends on whether you actually have the hardware and want to use it... For me, with an integrated Vibra 16 on the mobo, Voxware is now unusable for sound as the SoundBlaster portion is not recognised. (Again, only in -current, it all works perfectly in -stable). I /have/ to use pcm in -current, simply to play CDs (which, incidentally, works well for me)... Of course, for the time being, I have the option of using this hardware under -stable, but eventually the changes will filter through to there as well. Of more importance (to me, right now), is that -stable is not getting the benefit of the other improvements that are going on in -current. (e.g. Linux threads, SMP, NFS etc.) Cheers, AS To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
