Tapan,
At first glance, I see no difference in the I/O memory layout between
your Silicon 537 [Winmodem] board and Ryan's true Intel's 537 modem.
Here is yours:
$ /sbin/lspci -vvv
...
04:00.0 Modem: SILICON Laboratories Intel 537 [Winmodem] (rev 04) (prog-if 00
[Generic])
Subsystem: SILICON Laboratories Device 3000
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping+ SERR- FastB2B+ DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32 (250ns min, 15500ns max), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 21
Region 0: Memory at 50001000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at 1000 [size=256]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Here is Ryan's:
ryan@Ryan:~/intel-536-537$ sudo lspci -vvv
'''
01:01.0 Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI (rev
04)
Subsystem: Dell Device 1000
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping+ SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 22
Region 0: Memory at feafe000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at de00 [size=256]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
'''
So the exact same Region 0 and Region 1 features, only except the addresses.
I do remember from our mails exchange if you kept them all, than another
driver was responding to
$ stty -F /dev/modem -a
I do also remember that efax was responding after some kernel oops.
I do remember I modified two files to get your hardware possibly handled :
1/ I added "case TJ320_VENDOR_ID + 1:" to coredrv/afedsp_int.c. This was
my very first modification to enable your Silicon 537 board recognized.
2/ And I modified several times coredrv/coredrv.c to attempt and
finally succeed to unregister the "serial" driver which was conflicting.
I also do remember that prior to succeeding to get rid of the serial driver via
a kernel call to unregister it (my latest coredrv.c), you have set 8250.nr_uarts=0
in /boot/grub/grub.conf to your kernel boot parameters. I was suggesting
8250.nr_uarts=1. Before my coredrv.c last change, this was NOT correctly
working as despite 8250.nr_uarts=0, the 8250_pci.c alias "serial" driver was
still calling pci_enable_device which reflected as a PCI entry for IRQ 21 in your
/var/log/messages
So the thing I would suggest you as now we have some certainties is that you:
First you add 8250.nr_uarts=0 to your kernel boot parameters in your /boot/grub/grub.conf.
Next reboot.
Next after reboot:
$ cd intel-536-537/
$ make 537
$ sudo make uninstall
$ sudo make install
$ ls -l /dev/modem (should point to /dev/537ep)
$ ls /dev/537ep* (there should two devices)
$ stty -F /dev/modem -a
$ ls -l /dev/modem
$ ls /dev/537ep*
$ efax -vewinchmart
Staying tuned.
-
http://vouters.dyndns.org:8080/
Philippe Vouters (Fontainebleau/France)
