Hello,
is there any way to obtain source code for Tulip driver? I have a card
that does not work with tulip (SOHOWare) and I thought of fixing the
driver, But I certainly do not want to develop driver from scratch.
Why did not you include all the drivers in DDK?
Thanks, Slava
Many of the drivers have NDAs assocaited with them. That is why not all
of the drivers are included. What chipset is on te SOHOWare card?
chris
slavka <slavka012@yahoo.ca> wrote:
Hello,
is there any way to obtain source code for Tulip driver? I have a card
that does not work with tulip (SOHOWare) and I thought of fixing the
driver, But I certainly do not want to develop driver from scratch.Why did not you include all the drivers in DDK?
Thanks, Slava
–
cdm@qnx.com > “The faster I go, the behinder I get.”
Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
The chip is MX98715. When I start the io-net with the driver, it
correctly detects the card but selects media “MII No Link”. All the PCI
related parameters are correct. Forcing media to anything else results
in “Media not found, defaulting to autodetect” and then again “MII No
Link”.
I’ve found linux source of the driver for the chip, but the diffence
between the systems is too big for the porting of the driver to be an
easy task. I understand there are some problems with the QNX tulip
driver, I saw similar reports with other cards, but I did not see
reports it’s been fixed. It’s a pity source code is not accessible, as
now I can only hope someone will fix it some time soon.
Thanks, Slava
Chris McKillop wrote:
Many of the drivers have NDAs assocaited with them. That is why not all
of the drivers are included. What chipset is on te SOHOWare card?chris
slavka <> slavka012@yahoo.ca> > wrote:
Hello,
is there any way to obtain source code for Tulip driver? I have a card
that does not work with tulip (SOHOWare) and I thought of fixing the
driver, But I certainly do not want to develop driver from scratch.Why did not you include all the drivers in DDK?
Thanks, Slava
Chris,
This is the same issue I’ve been having for some months now (since July). I
also get the MII No Link message with the identical issues when trying to
change media type via the “media=” parameter. My chipset is 2500 (Abocom
a.k.a. SMC8035TX).
You can reference my posts in “qdn.public.qnxrtp.installation” (Help with
SMC 8035)and “qdn.public.qnxrtp.os” (Trouble with devn-tulip.so).
Near as I can tell, the Media Sense tables aren’t being enumerated/detected
correctly?
Alex
“slavka” <slavka012@yahoo.ca> wrote in message
news:3C0F058C.7090603@yahoo.ca…
The chip is MX98715. When I start the io-net with the driver, it
correctly detects the card but selects media “MII No Link”. All the PCI
related parameters are correct. Forcing media to anything else results
in “Media not found, defaulting to autodetect” and then again “MII No
Link”.I’ve found linux source of the driver for the chip, but the diffence
between the systems is too big for the porting of the driver to be an
easy task. I understand there are some problems with the QNX tulip
driver, I saw similar reports with other cards, but I did not see
reports it’s been fixed. It’s a pity source code is not accessible, as
now I can only hope someone will fix it some time soon.Thanks, Slava
Chris McKillop wrote:
Many of the drivers have NDAs assocaited with them. That is why not all
of the drivers are included. What chipset is on te SOHOWare card?chris
slavka <> slavka012@yahoo.ca> > wrote:
Hello,
is there any way to obtain source code for Tulip driver? I have a card
that does not work with tulip (SOHOWare) and I thought of fixing the
driver, But I certainly do not want to develop driver from scratch.Why did not you include all the drivers in DDK?
Thanks, Slava
\