My 2c worth -
I have the ESS ES2898 modem chipset working very well under LinuxBIOS. There
was one main reason for selecting this device, my hardware platform is a
little low on processing power, therefore I was looking for a DSP modem
chipset - The ES2898 has the DSP built in to it. After a few hiccups with
drivers, ESS managed to get it right and it works fine now.
Hamish
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Ollie Lho
Sent: Monday, September 03, 2001 4:19 AM
To: Nikolai Vladychevski
Cc: [EMAIL PROTECTED]
Subject: Re: modems with linuxbios on sis730
Nikolai Vladychevski wrote:
>
>
> Problem under Linuxbios:
>
> When using the modem, the driver can't get IRQ for the device. All of the
> drivers display "using irq=0" in dmesg and an empty minicom screen appears
>
It is still the problem of those broken driver. The do not respect the
Linux Kernel's way of accessing PCI configuration space. Your problem
is the they are try to access the Interrupt Line, 0x3C in the
configuration
space directly for the hardware. But unfortunately the kernel does not
"save" this value in the hardware, it is cached in the internal data
structure. Why don't those driver do it in ther right way ?? Becasue
they just "reused" the WinXX driver.
> Some toughts:
>
> Maybe it is because Sis730 chipset is not fully supported by the kernel at
> this time, from dmesg:
>
> SiS pirq: advanced IDE/ACPI/DAQ mapping not yet implemented
>
> I checked the kernel sources until 2.4.9, support for advanced
IDE/ACPI/DAQ
> mapping still not yet implemented.
> And I don't think it will be supported soon since the comment says, "Bios
> already does that stuff"
> Nothing on alan cox kernels also...
>
It is not neceressary for an IRQ routing table for IDE device. Since
they are routed to int 14 and 15 for IDE and the IDE driver knows about
that.
> About the drivers:
>
> Unfortunately no 100% opensource drivers for the well known modem chipsets
> exist at this time. Since that is a propietary technology the companies do
> not want to open it. PCTEL even has a patent on his modem operation.
> The only opensource part is the serial device driver, that all the modem
> manufacturers grab from serial.c that located in linux kernel tree, modify
> it linking with they propietary calls and that's how all they work.
>
I suggest you use an external modem if you don't have any boardband
access.
If you have boardband access just connect your cable/ADSL modem to the
ehternet.
As for your experiment, I don't think you can do it this way. DIfferent
modem card with assert different Interrupt Pin (INTA - D), these pins
are mapped to different Interrupt Line accroding to which PCI slot
they are. There is only thing you can try.
1. Boot with LinuxBIOS
2. use lspci to see how kernel assign the IRQ
3. use setpci to write the irq line to 0x3C
4. load your modem driver.
Good luck.
Ollie
