I've seen things you people wouldn't believe. You writing:
>> eisa_bus_match dev sig='HWPC061' state=0x1 eids=HWPF180
>> eisa_bus_match dev sig='HWP1940' state=0x3 eids=HWPF180
>> without:
>> eisa_bus_match dev sig='HWPC061' state=0x1 eids=HWPF180
>> eisa_bus_match dev sig='HWP1940' state=0x0 eids=HWPF180
>> when modprobing hp100.
>The name HWP1940 is in the table, so that looks okay.
>Can you build with HP100_DEBUG defined?
OK. I builded module from 2.6.4-rc2 with HP100_DEBUG defined.
During compilation:
drivers/net/hp100.c: In function `hp100_eisa_probe':
drivers/net/hp100.c:2875: warning: unsigned int format, long unsigned int arg
(arg 3)
drivers/net/hp100.c: In function `hp100_module_init':
drivers/net/hp100.c:3066: warning: label `out3' defined but not used
drivers/net/hp100.c: At top level:
drivers/net/hp100.c:2806: warning: `hp100_RegisterDump' defined but not used
after modprobe hp100 I'm getting just:
bus eisa: add driver hp100
nothing more (I added CONFIG_DEBUG_DRIVER to kernel config).
The same on 2.6.4-rc1 (without any message after loading module).
--
,d$$$$$P.d$$b d$P ,gd$$$$$,gd$$$$g. ,$$$b._$$P RLU #172534
ggggggggggggg. ggs ,gg ,gg ,gg ggp,ggggg Paweł Sokołowski
d$P""""'""""Y$$. d$P d$P d$P ,d$Pd$P `Y$$P falcon@xxxxxxxxxxxxxxx
d$P Y$$d$$$$$P`Y$$$$$'`Y$$$$$P'd$P d$P Replicant (M) Des: Falcon
|