From: "John Poltorak" <os2-wireless_users@2rosenthals.com>
Date: Sat, 5 Aug 2006 20:43:17 +0100
To: Steven Levine <os2-wireless_users@2rosenthals.com>
Subject: Re: [OS2Wireless]Re: PCMCIA help
Message-ID: <20060805204317.B46@warpix.org>
References: <list-271888@2rosenthals.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <list-271888@2rosenthals.com>; from Steven Levine on Sat, Aug 05, 2006 at 10:32:24AM -0700


Hi Steven,

On Sat, Aug 05, 2006 at 10:32:24AM -0700, Steven Levine wrote:
> In <list-270792@2rosenthals.com>, on 08/05/06
>    at 01:33 AM, "John Poltorak" <os2-wireless_users@2rosenthals.com> said:
> 
> Hi John,
> 
> >Yes, there looks to be quite a lot of useful stuff, but nowhere to ask 
> >questions.
> 
> You can ask here.
> 
> >I get the impression that my controller card is supported out of the box 
> >with Warp 4, but it doesn't work. I'd like to know what I'm doing wrong.
> 
> In the hope of not muddling things worse than they already are.
> 
> There are two kinds of PCCard interfaces.  The older 16-bit PCMCIA
> interface and the current Cardbus interface, which is usually 32-bit.
> 
> There are two kinds of PCCard drivers.  Socket services compliant and
> point enabled.  Socket services compliant drivers require a socket
> services driver (i.e. IBM2SS14.SYS etc.).
> 
> Point enabled drivers do not require a socket services driver.  They
> contain code to power up the PCCard and assign fixed resources.  They
> rarely contain APM support, so typically you can not suspend and resume.
> 
> Some drivers include code for both Socket Services support and point
> enabled use.
> 
> A given point enabled driver written in the days of 16-bit PCMCIA sockets
> may or may not work in a Cardbus socket.  We do not live in a perfect
> world.
> 
> First thing you need to do is find a driver for the Token Ring card.

That's the easy bit. I've been using the card for about 7 years in a 
ThinkPad 600 

The driver is IBMTOKCS.NIF. I pretty certain it's a 16-bit card.

 
> Next you need to figure out if the driver requires socket services or if
> it is point enabled.  If it is only point enabled, you may be out of luck. 
> The driver will either work or not.

I think it does require a socket services driver.
 
> If the driver is point enabled only and the driver does not work, your
> next task is try Veit's cbenable.  If may be able to power up the socket
> sufficiently for the driver to work.
> 
> If the driver is Socket Services compliant, you need to track down a
> Socket Services driver for your Cardbus socket controller (i.e. the
> Ricoh).  It may or may not exist.  My sources say you need to use the
> Socket Services driver for the Lattitude CPX, C600 or C610 models.  This
> is at the Dell site.

I have little confidence in finding anything I need at Dell's website.

In any case I'm not aware of any cross reference table showing which 
socket services driver are used by which controllers. I doubt whether Dell 
would have anything for OS/2. And if they did, I wouldn't be able to find 
it.

According to 

http://www.os2warp.be/index2.php?name=pcmciaentry

There is a green tick in column 0 against Ricoh RL5C476, which AIUI 
suggest that I should be able to use this out of the box with Warp 4, but 
I can't see any reference to which driver to use.

I hope this is the correct chip. I got its ID using PCI.

 
> As I often tell you, you would really help yourself if you provided more
> specifics without being asked.  Exactly which token ring card are you
> trying to use and which PCCard driver are you using with it?  A link to
> the driver would be good.  The NIFs and readmes ofthen provide useful
> clues.

Thanks for your comprehensive explanation on how the PCCard interface 
works. As for my original question I thought I'd been sufficiently clear 
what I needed. Obviously not.

> 
> Steven
> 
> -- 


-- 
John