4This package includes a software-only device, called fmc-fakedev, which
   5is able to register up to 4 mezzanines (by default it registers one).
   6Unlike the SPEC driver, which creates an FMC device for each PCI cards
   7it manages, this module creates a single instance of its set of
  10It is meant as the simplest possible example of how a driver should be
  11written, and it includes a fake EEPROM image (built using the tools
  12described in *note FMC Identification::),, which by default is
  13replicated for each fake mezzanine.
  15You can also use this device to verify the match algorithms, by asking
  16it to test your own EEPROM image. You can provide the image by means of
  17the eeprom= module parameter: the new EEPROM image is loaded, as usual,
  18by means of the firmware loader.  This example shows the defaults and a
  19custom EEPROM image:
  21     spusa.root# insmod fmc-fakedev.ko
  22     [   99.971247]  fake-fmc-carrier: mezzanine 0
  23     [   99.975393]       Manufacturer: fake-vendor
  24     [   99.979624]       Product name: fake-design-for-testing
  25     spusa.root# rmmod fmc-fakedev
  26     spusa.root# insmod fmc-fakedev.ko eeprom=fdelay-eeprom.bin
  27     [  121.447464]  fake-fmc-carrier: Mezzanine 0: eeprom "fdelay-eeprom.bin"
  28     [  121.462725]  fake-fmc-carrier: mezzanine 0
  29     [  121.466858]       Manufacturer: CERN
  30     [  121.470477]       Product name: FmcDelay1ns4cha
  31     spusa.root# rmmod fmc-fakedev
  33After loading the device, you can use the write_ee method do modify its
  34own internal fake EEPROM: whenever the image is overwritten starting at
  35offset 0, the module will unregister and register again the FMC device.
  36This is shown in fmc-write-eeprom.txt