Vendor has x86 driver, am I asking for too much for ARM version?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



I want to use a USB Data Aquisition Module with a ARM based win CE 6.0 system

The USB DAQ manufacturer claims to have a x86 driver for CE 6.0

but claims they do not have an ARM version for the following reason:
""Since the USB performance in WinCE ARM system is poor..."
(I have a i.mx31 dev kit with 533 MHz ARM core)

any guesses what is going on? doesn't the driver simply get built with the
ARM processor selected instead of x86?

what is the magnitude of effort that I would be asking of the vendor to make
a ARM driver given that they already have a presumably working x86 CE 6.0
version?

at worst couldn't they rebuild the drivers with my platform's SDK?

any good questions I should ask them?


.



Relevant Pages

  • Re: How to Interface to USB
    ... said I did this on an ARM 9 not an Intel or AMD with windows controlling the ... USB Bus:). ... I guess engineering my own driver for *each* device is ... >> will have to get ahold of the company that produces the actual GPS. ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Do I always need an SDK in order to build drivers?
    ... The USB Stack itself takes care of any hardware specifics, so your USB Scanner Driver is generic for all platforms. ... This means that a version compiled for ARM should work on all ARM platforms. ... I had the customer export an SDK from Platform Builder and send it to me. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: How to simulate an ARM architecture to test Driver...
    ... if you don't have any way to rebuild your driver for x86 target, ... other way than using an ARM based platform: the ARM binary code won't be ... Concerning the requirement of having the exact platform, ... > No substitution or simulation that I can make use of on x86 PC? ...
    (microsoft.public.windowsce.platbuilder)
  • Re: USB mass storage and ARM cache coherency
    ... hence the ARM implementation of update_mmu_cachedoesn't flush ... before writing to a page cache page. ... The driver fix is as simple as calling a flush_dcache_pageand I've ... The only exception was an IDE ...
    (Linux-Kernel)
  • Re: USB mass storage and ARM cache coherency
    ... hence the ARM implementation of update_mmu_cachedoesn't flush ... the D-cache. ... Forget about PG_arch_1 and always do the flush? ... The driver fix is as simple as calling a flush_dcache_pageand I've ...
    (Linux-Kernel)