Subject: A TODO list for cardbus/ PCMCIA support.
To: None <>
From: Jonathan Stone <jonathan@DSG.Stanford.EDU>
List: tech-kern
Date: 06/16/1999 18:16:27
Here's a list I've been kicking around, of things that we should
do  to s

1.  The way Hayakawa-san's existing CardBus patches bus windows (i.e.,
    a bus bridge which only provdes access to a subset of the parent's
    bus-space on the bridged, child bus) is far from great.  I think
    Jason and i have said much the same idea about how to fix that,
    tho' we've said it in very different language. Basic idea
    is to have a bus-space tag keep track of the `window' on the
    bus in which the tag can acutally allocate space.

2.  Support for CardBus bridge chips which arent initialized properly
    by BIOSes. We can add support for `known' bridge chips as PCI
    devices, and configure them, but given the rate-of-change in the
    PCI world, that may be a losing battle as new bridge chips get
    introduced way faster than we can do releases.

3.  Integrated PCMCIA/CardBus `tuple space' support code.  (and
    anything else that should be shared between cardbus and old-style

4.  Real support for hotswap, power on/off, etc.

5.  Fix bogons in existing PCMCIA code: e..g., eliminate long delay()s
    in interrupt context. 

6. The ongoing problems with allocating IRQs, IOports,  etc.
   for PCMCIA bridges. (explicit support for a pnpbios,
   attaching pnp devices *before* ISA devices,  may or may not help here).

I know there are a variety of projects underway which address some of
these points. And some have languished for ages. 
What we really need is some co-ordination --
especially if we want to get these out `for the next release'.

So, can anyone working on any of these  please speak up?