Re: Heads up for distro folks: PCMCIA hotplug differences (Re: -rc4: arm broken?)

From: Russell King (rmk+lkml_at_arm.linux.org.uk)
Date: 08/01/05

  • Next message: Shaohua Li: "Re: [ACPI] S3 and sigwait (was Re: 2.6.13-rc3: swsusp works (TP 600X))" 
    Date:	Mon, 1 Aug 2005 07:48:31 +0100
To: Alan Cox <alan@lxorguk.ukuu.org.uk>

    On Mon, Aug 01, 2005 at 02:01:07AM +0100, Alan Cox wrote:
    > On Sad, 2005-07-30 at 22:36 +0100, Russell King wrote:
    > > Since PCMCIA cards are detected and drivers bound at boot time, we no
    > > longer get hotplug events to setup networking for PCMCIA network cards
    > > already inserted. Consequently, if you are relying on /sbin/hotplug to
    > > setup your PCMCIA network card at boot time, triggered by the cardmgr
    > > startup binding the driver, it won't happen.
    >
    > So eth0 now randomly changes between on board and PCMCIA depending upon
    > whether the PCMCIA card was inserted or not, and your disks re-order
    > themselves in the same situation. That'll be funny if anyone does a
    > mkswap to share their swap between Linux and Windows. Gosh look there
    > goes the root partition.
    >
    > I'm hoping thats not what you are implying. Especially for disks,
    > network is much much less of an issue.

    If you have the socket driver as a module, as some (most?) distros do,
    then of course such cards won't be detected at boot time. If PCMCIA
    and the socket driver are built-in, along with the card driver, then
    I guess this possibility may well exist - it does for NE2K cards.

    Since I don't use CF cards with PCMCIA here, I can't say what the ide-cs
    behaviour actually is. This is why I'm trying to encourage folk to
    explore the kernels new behaviour. 

    -- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
  • Next message: Shaohua Li: "Re: [ACPI] S3 and sigwait (was Re: 2.6.13-rc3: swsusp works (TP 600X))"

    Relevant Pages

    • Re: VxWorks 6.6 - Ethernet interface driver support
      ... Ethernet interface cards, deploying the "Intel PRO/1000 VxBus Enhanced ... Network Driver" in conjunction with the "Generic PHY driver", ... these interfaces. ...   MII_Bus @ 0x005073cc ...
      (comp.os.vxworks)
    • [patch] v4l: cx88 driver update
      ... Finally the big cx88 driver update which makes the cx88-dvb ... driver compile and work for some cards. ... const unsigned int cx88_idcount = ARRAY_SIZE; ... struct btcx_riscmem *risc) ...
      (Linux-Kernel)
    • sd cards : OCR busy?
      ... on some other cards. ... My recent error is - the error OCR busy Error. ... OMAP OCPI interconnect driver loaded ... MMC1: OCR busy error, CMD55 ...
      (Linux-Kernel)
    • Re: VxWorks 6.6 - Ethernet interface driver support
      ... Ethernet interface cards, deploying the "Intel PRO/1000 VxBus Enhanced ... Network Driver" in conjunction with the "Generic PHY driver", ... out the fiber optic support saves a little bit of code space). ...
      (comp.os.vxworks)
    • Re: XXX_Init only being called once
      ... > My stream interface driver has been stripped right back to try to solve ... > I plug my card in the first time. ... > There are two new active keys in the registry PCMCIA and myDriver. ... > No entry points are called in my driver. ...
      (microsoft.public.windowsce.platbuilder)
    Loading