Re: Behavior of AVStream after returning STATUS_PENDING from Process routine
From: Max Paklin (mpaklin_at_hotmail.com)
Date: 06/01/04
- Next message: Max Paklin: "Re: AVStream: Using InterlockedAnd(), InterlockedOr(), InterlockedXOR()"
- Previous message: Niklas: "Re: NDIS WPA TKIP Problem"
- Next in thread: Panda Ng: "Re: Behavior of AVStream after returning STATUS_PENDING from Process routine"
- Reply: Panda Ng: "Re: Behavior of AVStream after returning STATUS_PENDING from Process routine"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 1 Jun 2004 00:58:52 -0700
> I write my driver with reference to the AVStream example "avssamp". I
didn't see this flag is set. And no "pointer advance" in the process
routine.
>
> Moreover, is pin-centric topology more favourable then filter-centric? My
driver is for my hardware but actually I do nothing to route data in a
"pin", just read a frame in RGB format from my harware when an interrupt
occurs.
Oh, I missed the part where you said that you were working with
filter-centric minidriver.
I don't know much about it.
A wild guess would be that something is wrong with pin flags, but I can be
totally off.
Honestly I never figured out a point of using filter-centric approach except
for transform hardware-less drivers.
-- Max.
- Next message: Max Paklin: "Re: AVStream: Using InterlockedAnd(), InterlockedOr(), InterlockedXOR()"
- Previous message: Niklas: "Re: NDIS WPA TKIP Problem"
- Next in thread: Panda Ng: "Re: Behavior of AVStream after returning STATUS_PENDING from Process routine"
- Reply: Panda Ng: "Re: Behavior of AVStream after returning STATUS_PENDING from Process routine"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|