Re: Incorporating a 3rd party driver into a BSP/Image



Hang on. It's binary files, right? Put it in platform.bib and everything
will go into the \Windows folder (that's the only choice and
non-negotiable). If you need to have the files *copied* from \Windows to
some other location at run-time, you can do that with entries in the
platform.dat file.

As far as 'making it part of my BSP', I'm not sure what that means to you.
You're going to ship this BSP to others for use in creating their own OS
configurations for your hardware? If not, you can put the entries for your
driver into its own catalog item and add/remove them from any OS
configuration, regardless of what BSP it's targeting.

Can we know what WiFi card we're talking about?

Paul T.

"Roger Williamson" <RogerWilliamson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:555E2858-0C80-4490-9E07-E3D14C32A3DE@xxxxxxxxxxxxxxxx
I have a .CAB file which installs a WiFi card driver onto the CE device I'm
developing. I've been able to extract out all the binary files, and the
registry changes necessary to get the driver up and running, but I've run
into a problem.

I don't know how to incorporate a binary-only driver into a BSP
(especially
not one with several components which installs itself across
subdirectories
in the \Windows folder)

Even worse, the word from higher-ups says I have to get rid of the CAB
support since it is taking up too much space, so I have to incorporate
this
driver into my image at least, even if it is impossible to make it part of
the BSP.


.



Relevant Pages

  • Re: Incorporating a 3rd party driver into a BSP/Image
    ... any sample code, I though we were talking about a the Summit binaries. ... folder and run? ... As far as 'making it part of my BSP', I'm not sure what that means ... driver into its own catalog item and add/remove them from any OS ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Incorporating a 3rd party driver into a BSP/Image
    ... I looked at that help file, ... folder and run? ... You're going to ship this BSP to others for use in creating their own OS ... driver into its own catalog item and add/remove them from any OS ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Incorporating a 3rd party driver into a BSP/Image
    ... I am now able to configure the file system, and by extension get all of my ... driver suite actually run as if a CAB had installed it. ... folder and run? ... As far as 'making it part of my BSP', I'm not sure what that means ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Incorporating a 3rd party driver into a BSP/Image
    ... I see what my problem was with the extra directories, ... create a folder for them in my release directory in the hope that the folder ... The higher ups at the company want the driver added to the BSP because ... As far as 'making it part of my BSP', I'm not sure what that means to you. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Incorporating a 3rd party driver into a BSP/Image
    ... I don't think I'm modifying the right platform .dat file, ... BSP, at least any with an ARM processor in it). ... Since the driver has *no* ... create a folder for them in my release directory in the hope that the ...
    (microsoft.public.windowsce.platbuilder)

Loading