Messages in this thread | | | Date | Wed, 9 Aug 2000 11:57:53 -0700 | From | David Hinds <> | Subject | Re: [PATCH] aironet4500_cs.c kmalloc checking |
| |
> Could anyone point me some reading material, which would tell: > 1. why most of pcmcia drivers have the same(huge) amount of about > same code at initialization/cleanup ?
Most of the pcmcia drivers have similarly structured initialization and cleanup code, but if you look closer, you'll see that it is not the same.
> 2. What all of those structures/functions mean and under what circumstances > may be called and so on ?
You did write this driver, right?
The Linux PCMCIA web site (pcmcia-cs.sourceforge.net), and every distribution of the pcmcia-cs package, includes the Linux PCMCIA Programmer's Guide, which is 72 pages of API documentation, including a walk-through of all the components of a PCMCIA client driver. The PCMCIA package also includes a heavily commented skeleton driver (dummy_cs).
> could I get pcmcia network card initalized with same amount of codelines > as ISA and PCI ?
No, you can't.
But then regular ISA and PCI drivers don't support hot plug devices that are configured dynamically. There is a hot plug PCI interface in 2.4, that also works for CardBus cards, but so far only a few drivers use it. And the problems are still being sifted out of that. For 16-bit PCMCIA cards, configuration is a lot more complicated than for PCI devices.
> 4. I'd like to play with acpi/APM a bit, any ref implementations > for pcmcia ?
For PCMCIA drivers, ACPI/APM is handled for you. You just field CS_EVENT_SUSPEND and CS_EVENT_RESUME events in your PCMCIA event handler.
> 5. Is there a way to avoid cardmgr, i.e. for boxes which have 4 > cards in and they probably will stay there forever
At the moment, no, you can't do that.
-- Dave Hinds
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |