Hi, all.
I want to do image processing in kernel driver.
For example, I want to fill gray some area of dc in the function HookedNtGdiBitBlt that I hooked by ssdt hooking.
This is not a specific question.
I’m asking the possibility and , in addition, how can I research or start jobs to make a goal.
unless you have device installed capable of processing the image, there is
no need for processing in SW in the kernel mode driver as it is CPU
intensive.
On Jan 17, 2008 10:59 AM, wrote:
> Hi, all.
>
> I want to do image processing in kernel driver.
>
> For example, I want to fill gray some area of dc in the function
> HookedNtGdiBitBlt that I hooked by ssdt hooking.
>
> This is not a specific question.
> I’m asking the possibility and , in addition, how can I research or start
> jobs to make a goal.
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
xxxxx@gmail.com wrote:
I want to do image processing in kernel driver.
Philosophically speaking, this is a bad idea. The only things that
should be in kernel code are things that MUST be in kernel mode.
Everything else must be in user-mode code.
WHY do you want to do image processing in kernel code? What problem
will this solve?
For example, I want to fill gray some area of dc in the function HookedNtGdiBitBlt that I hooked by ssdt hooking.
No, you don’t, unless your graphics hardware is broken, and in that case
you wouldn’t hook at that level anyway; you’d catch it inside the
display driver, where you can call EngBitBlt to do the work.
This is not a specific question.
I’m asking the possibility and , in addition, how can I research or start jobs to make a goal.
You’ve committed the same sin as Nayan here. Instead of sharing the
overall requirement and asking for possible architectures, you have
zoomed in to focus on one possible implementation, and asked how to
accomplish that. Take a step back, and let’s try to figure out what you
are actually trying to do.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.