[wdmaudiodev] Re: Audio OUT on Longhorn
- From: "Martin Puryear" <martinp@xxxxxxxxxxxxxxxxxxxxx>
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Sat, 16 Jul 2005 13:43:28 -0700
KS.SYS and all its compatriots (KSUSER.DLL, KSTHUNK.SYS, KSPROXY.AX,
etc) are all still there in Longhorn.
The only removals that I know of besides the audio-specific ones
(sysaudio, kmixer, splitter, etc) are a few removals of really old HW -
such as a 1999 WDM Video driver for HW-based MPEG-2 decode, found only
on certain laptops. All the vidcap infrastructure pieces (stream.sys,
mspclock, etc) are still there.
MartinPuryear
Software Architect
Development Lifecycle
Windows CoreOS Division
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Matt Gonzalez
Sent: Friday, July 15, 2005 12:45 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Audio OUT on Longhorn
OK, thanks, Hakon. That's a relief!
Matt
Hakon Strande wrote:
Sorry, I was too generic in my statement. This only applies to
audio
only components. Ks.sys services other device classes as well
and is
still there as far as I know.
In the case below the AVStream driver may be (I am speculating)
exposing
a topology that was interpreted by sysaudio in XP and other
released OS
but is currently not by the new audio components in LH. If we
had a
device and a driver we could investigate this regression. We
don't like
regressions that create more work for you guys of course.
Sincerely
Hakon Strande
PM Integrated, Internal, External, and Wireless Audio Devices
MediaTech/DMD/Windows Client/Microsoft
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Matt
Gonzalez
Sent: Friday, July 15, 2005 12:09 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Audio OUT on Longhorn
Hello Hakon-
Could you please clarify something? You state that only
portcls.sys and
the miniport driver are left in the kernel for Longhorn. What
about
AVStream support - doesn't that require ks.sys?
The reason I ask is that the audio driver for our 1394 hardware
is based
on the AVStream model.
Matt
Hakon Strande wrote:
Dear Sir,
The Windows Audio system has been completely re-designed
for Longhorn
to
better enable high fidelity, transparency, stability,
glitch resilience
and low latency. All audio kernel components (like the
well-known
kmixer.sys and sysaudio.sys, etc) are gone and the
functionality moved
to user mode, the only components left in the kernel is
the audio
helper
library PortCls.sys and the miniport driver itself.
This may be the cause of your problem depending on what
you mean by
"AVS
WDM". Longhorn audio system documentation will most
likely be available
sometime during the Beta 2 time frame but compatibility
goal with
legacy
drivers is 100% so if you have issues please file bugs
through the beta
program.
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/
****************** WDMAUDIODEV addresses: Post message:
mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator:
mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/
Other related posts:
