Re: Intel 537EP - driver loads but cannot use modem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Bjorn,

The 537EP driver for Chris problem (top of stack trace si3052Init) ought
to fail to initialize the SI3052 chip described at
http://www.silabs.com/Marcom%20Documents/Resources/Si3052_PB.pdf

One of the features of this chip is the following : 32-bit, 33 MHz, PCI
2.3 compliant interface. So Chris, can you tell us whether your PCI is
32 bits, 33MHZ and 2.3 compliant ???? See the specs of your computer.

Regards,
-- 
sip:Vouters.Philippe@xxxxxxxxx
IM: philvout (Yahoo!)
http://vouters.dyndns.org/
Philippe Vouters (Fontainebleau/France)



-------- Message initial --------
De: Bjorn Wielens <Uniacke1@xxxxxxxx>
À: Philippe Vouters <Philippe.Vouters@xxxxxxxxxxx>
Cc: Antonio Olivares <olivares14031@xxxxxxxxx>, Chris Tracy
<chris.t.tracy@xxxxxxxxx>, discuss@xxxxxxxxxxxxx, Marvin Stodolsky
<marvin.stodolsky@xxxxxxxxx>
Sujet: Re: Intel 537EP - driver loads but cannot use modem
Date: Sun, 07 Mar 2010 16:30:04 -0400

I wonder if this is the same issue I ran in to last year when I picked
up such a modem...
Also identified as a 537, but the board itself was from a Dell system,
and branded "537EPG".

Chris, can you examine the back of your board? Does it say "537EP" or
"537EPG"?

If there are distinguishing marks, it will at least be easier to
determine whether this is a hardware or a software limitation.

Bjorn.


On 03/07/2010 04:11 PM, Philippe Vouters wrote:
> 
> Antonio,
> 
>>From intel-536-537/makefile_537, PCIDEV=8086:1080 well corresponds to a
> 537EP modem absolutely handled by the
> http://vouters.dyndns.org/Intel/intel-536EP-537EP_2010_01_06.tar.bz2
> What brings an uncertainty between 536EP and 537SP is PCIDEV=8086:1040
> 
> Now Chris is facing a problem with his 537EP modem in modem_init (see
> kernel stack trace).
> 
> There is not much I can do to help as the code involved resides in
> 537_core.lib which has always been Intel's proprietary code and shipped
> in binary format. This is all the problem with Winmodems.
> 
> Regards,




[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux