Hello friends,
I have looked through the documentation a bit more, and I am having trouble
figuring out how to proceed with Windows Phone driver development.
In the WDK, I can see options for building for ARM, and for building UEFI
applications. However, approaching development is still rather opaque. Are
kernel facilities the same?
In this case, please assume that the not-consumer-controlled Secure Boot of
these platforms is not an issue.
Cheers,
R0b0t1
You want to write a universal driver
https://docs.microsoft.com/en-us/windows-hardware/drivers/develop/getting-started-with-universal-drivers
d
Bent from my phone
From: xxxxx@lists.osr.com on behalf of xxxxx@gmail.com
Sent: Monday, April 9, 2018 6:55:34 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Mobile Drivers
Hello friends,
I have looked through the documentation a bit more, and I am having trouble figuring out how to proceed with Windows Phone driver development.
In the WDK, I can see options for building for ARM, and for building UEFI applications. However, approaching development is still rather opaque. Are kernel facilities the same?
In this case, please assume that the not-consumer-controlled Secure Boot of these platforms is not an issue.
Cheers,
R0b0t1
— NTDEV is sponsored by OSR Visit the list online at: MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers! Details at To unsubscribe, visit the List Server section of OSR Online at
Now… THERE’s a topic I haven’t had anyone ask me in, oh, two or three years at least…
Yes. What Doron said: Write a Universal Driver. The rest of it… it’s Windows.
Now… having SAID that… if you’re REALLY writing driver(s) for phone, there are lots of very interesting power management issues, if you want to wring the last bits of efficiency out of those batteries. Always On/Always Connected… AKA Connected Standby/Modern Standby… Can make things a bit complicated.
But even THEN… these things aren’t different from ANY Windows platform these days. Windows Phone really is Windows… but a very carefully intedgrated and optimized Windows.
Peter
OSR
@OSRDrivers
Thanks Mr. Horan, Mr. GV. I remember the documentation touching on
that. It blended together well enough it slipped my mind.
I don’t suppose there are mobile driver examples I missed?
It is a pity the platform is winding down, I quite liked it.
On Mon, Apr 9, 2018 at 1:41 PM, xxxxx@osr.com wrote:
>
>
> Now… THERE’s a topic I haven’t had anyone ask me in, oh, two or three years at least…
>
>
>
>
>
> Yes. What Doron said: Write a Universal Driver. The rest of it… it’s Windows.
>
> Now… having SAID that… if you’re REALLY writing driver(s) for phone, there are lots of very interesting power management issues, if you want to wring the last bits of efficiency out of those batteries. Always On/Always Connected… AKA Connected Standby/Modern Standby… Can make things a bit complicated.
>
> But even THEN… these things aren’t different from ANY Windows platform these days. Windows Phone really is Windows… but a very carefully intedgrated and optimized Windows.
>
> Peter
> OSR
> @OSRDrivers
>
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at http:</http:></http:></http:>
Well… again… the drivers for Windows Mobile aren’t particularly “special” in design or architecture. They’re just Windows Universal Drivers. Which is what makes them cool.
The only thing that might make them SORT OF different is the particular technologies they support. SO, for example, you probably don’t have an accelerometer on your desktop system, but you almost certainly have one on your phone. So, an I2C or SPI connected accelerometer would be a “phone device.”
In general, there are more “cute” peripherals like this that are SPB-connected on phones… though I expect the use of SPBs to connect peripherals on laptops and desktops to increase… and there’s nothing “special” about the fact that the devices are connected on a phone.
Peter
OSR
@OSRDrivers
On Wed, Apr 11, 2018 at 10:39 AM, xxxxx@osr.com wrote:
>
>
> Well… again… the drivers for Windows Mobile aren’t particularly “special” in design or architecture. They’re just Windows Universal Drivers. Which is what makes them cool.
>
> The only thing that might make them SORT OF different is the particular technologies they support. SO, for example, you probably don’t have an accelerometer on your desktop system, but you almost certainly have one on your phone. So, an I2C or SPI connected accelerometer would be a “phone device.”
>
Right, I should have said something that made better reference to
device classes that you might find more commonly on phones. I suppose
I could look at some Windows IoT stuff.
> In general, there are more “cute” peripherals like this that are SPB-connected on phones… though I expect the use of SPBs to connect peripherals on laptops and desktops to increase… and there’s nothing “special” about the fact that the devices are connected on a phone.
>
Expecting this, but was also interested in any proprietary on-chip
interconnects that may exist, though I suspect details on those will
not be forthcoming. Most devices seem to be (directly) memory mapped
now, anyway.
Cheers,
R0b0t1
> Peter
> OSR
> @OSRDrivers
>
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at http:</http:></http:></http:>