Hello list,

I'm currently looking for a more convenient method to use and choose Windows
drivers from a collection like BTS DriverPacks.net, different than one
provided in the unattended wiki
(http://ubertechnique.com/unattended/BTS_Driver_Packs).

What I'm thinking about is to use the Linux PCI devices informations
(from /sys/bus/pci/devices) on the hardware platform to install and try to
guess which .inf Windows drivers can match for each of these PCI devices via
their PCI_{VENDOR,DEVICE,SUBSYS,SUBDEV,CLASS} values.

By such a method, we guess what drivers should be interresting for Windows
support of our system and let it's plug-and-pray choose the right driver.

Example:
  $ lspci |grep Ethernet
  40:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit 
Ethernet PCI Express (rev 01)

  $ lspci -n |grep ^40:
  40:00.0 Class 0200: 14e4:1677 (rev 01)

  So I would have just to search in .INF Windows files which mathc the string
  "PCI\VEN_14e4&DEV_1677" in the whole (uncompressed) DriverPacks collection 
for instance.

  At least the following file match:
  driverPacks/D/L/B1/b57win32.inf    

  So unattended will just have to copy driverPacks/D/L/B1/ (and its content) as
  folder $oem$\$1\1\ of the hard drive and tell OemPNPpath to point to make
  Windows install my network card.

  If several .inf were matching (from distinct folders), we should just have
  to copy all of these folders (and let's Windows choose the "right"
  driver).

  And so one for all other PCI devices of my system (folders $oem$\$1\2\, ...).

The advantages should be:

- really comfortable to find easily the right (or good candidate) drivers
  for the whole hardware platform to install

- really quick: compute take 10s to parse the whole driverPacks.net driver
  collection

- reduce drastically the amount of files to copy onto hard drive, like 50MB
  compared to 300/500MB of compressed archive.

- really easier to maintain a site Windows database driver: "just"
  have to add a driver in the collection if it's missing.

I will be really interrested about any comments, advices and so on,
especially from people that have a good knowledge of Windows drivers
installation and driver .INF file content !

Perhaps I've missed an important point that make it a nonsense ? 

Thanks for your comments, returns, inputs or hints.

Regards,

Pierre Bourgin

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
unattended-devel mailing list
unattended-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-devel

Reply via email to