RE: New driver model in 2.6

spi_register_board_info() will add the board information structure to=20
board_list in drivers/spi/spi.c. The list is walked from

scan_boardinfo() in=20

the same file when a SPI master is registered by spi_register_master().

The=20

first step would be to check if spi_register_master() is called, and if

it=20

fails before calling scan_boardinfo(). Add a few printk's there.

If a master is correctly registered, scan_boardinfo() will call=20
spi_new_device(), which in turn calls device_register(). That's where

the=20

spi_match_device() function should be called, using the function

pointer=20

stored in proxy->dev.bus.match.

Thank you for your help, is it possible that calling
spi_register_master() before the spi_register_board_info() and before
the registration for m25p80 spi device causes the problem?=20

Thank you.