Thanks again for this and for supporting source codes. Unluckilly It appeared that I don't have SANA-II headers...
They're on the developer CD if you have it.
But I have looked though the sources this weekend (both 3C589 and pccardserial) and found them quite simmilar. So why couldn't it be integrated for combo PCMCIAs? I mean, I've read that its not possible because of card.resource limitations, but I don't see the reason.
Ok, not possible to have two drivers, sure, but single driver to work both as 3c589 and pcserial - why not?
It might be possible to have a combined driver, but IMO it'd be a messy solution. The only disadvantage of the current solution is that you can't use the modem and NIC
at the same time. Also, there are NE2000-compatible combo cards, so you could end up with cnet.device mixed in too!
I was also looking through these sources - The initialisation checks if the card is serial-compatible device by PRODUCT_INFO. 3c589 does it also, but for different device (562 or 589, if I'm correct).
Can multile function card be identified as both then? I mean the same byte canot have two values at the same time. Does it mean I won't be able to use modem, as 3c589.device has recognized it?
Combo cards should have multiple tuple chains, but card.resource doesn't support examining them. So the easiest way to identify combo cards is to look at the manufacturer and product codes (and include the codes of compatible cards in the driver).
By the way - where do you have that info about EtherlinkIII from? It's so precise. Don't tell me it's just your intuition. ;-) The same for PCMCIA itself. The same for UART...
3Com has programmer docs for most of their cards on their website. Information on PC-type UARTS is available in a lot of places, including text books and manufacturers' data sheets.
[/quote]