Moving from PCIe to Thuderbolt

[wd1]

Fwiw. We have written a wdf-based thunderbolt audio driver (stack) with custom hardware based on the Xilinx pcie core. The driver has undergone thunderbolt certification by Intel supporting windows 8.1 and 10. I can’t say that it has been without some minor hurdles along the way but I can say that there have been literally no “thunderbolt vs pcie” issues from the driver’s perspective other than actually having to correctly respond to pnp state changes that you don’t usually see in a static pcie card. Wdf obviously helps a lot there.

Sent from my iPhone

On Jun 20, 2015, at 01:58, Zvi Vered wrote:
>
> Dear Members,
>
> I owe you a huge apology.
>
> The FPGA I used had 2 BARs.
> The Thunderbolt interface did not “create” a BAR.
> An older FPGA version had one BAR and I thought by mistake that no one changed this.
>
> So in my private case, under Win7-64, the Thuderbolt interface works fine.
>
> Best regards,
> Z.V
>
> -----Original Message----- From: xxxxx@osr.com
> Sent: Tuesday, May 26, 2015 07:29 PM
> To: Windows System Software Devs Interest List
> Subject: RE:[ntdev] Moving from PCIe to Thuderbolt
>
>

> Thunderbolt is basically DisplayPort plus PCIExpress. With an
> appropriate (and relatively simple) bridge, it should just Plug-and-Play.
>

>
> That’s what I thought at first too, but on closer examination that is DEFINITELY NOT the case. There’s a lot more to it than that.
>
> About a year ago, we spent a lot of time looking into Thunderbolt on Windows. This time was ultimately not compensated as we wound-up having to decline the project.
>
> So, to repeat once again what I wrote above and what I know to be true as of one year ago:
>
>

> The last time I checked, and this was prior to Win10, Windows emphatically DID
> NOT generically support Thunderbolt. There are some significant technical issues, like
> having a PCIe root port just appear all of a sudden, that made supporting
> Thunderbolt “challenging.”
>
> There are some very limited and unique Thunderbolt implementations for some
> very specific things that have the necessary “stuff” to make them work with Windows. But there are soooo many potential issues here that, unless you’re partnering closely with a given vendor who’s providing the Thunderbolt support, I’m not sure why you’d be trying to get Thunderbolt
> anything working on Windows.
>

>
> Again, things might have changed in the past year or in Win10. But I know the above to be true as of one year ago. I am not guessing.
>
> Peter
> OSR
> @OSRDrivers
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> 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
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> 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