19 Feb, 2011

1 commit

  • After 2.6.34 changes, __pxa2xx_drv_pcmcia_probe() was replaced by
    sa1111_pcmcia_add(). That unfortunately means that configure_sockets()
    is not called, leading to MECR not being set properly, leading to
    strange crashes.

    Tested on pxa255+sa1111, I do not have lubbock board nearby. Perhaps
    cleaner solution exists?

    Signed-off-by: Pavel Machek
    Signed-off-by: Dominik Brodowski

    Pavel Machek
     

12 Dec, 2009

1 commit

  • ERROR: "pxa2xx_drv_pcmcia_ops" [drivers/pcmcia/pxa2xx_lubbock_cs.ko] undefined!
    ERROR: "pxa2xx_drv_pcmcia_add_one" [drivers/pcmcia/pxa2xx_lubbock_cs.ko] undefined!

    We also remove __pxa2xx_drv_pcmcia_probe and its export, since this is
    no longer required.

    Signed-off-by: Russell King

    Russell King
     

09 Nov, 2009

1 commit


29 Oct, 2006

1 commit

  • The PXA2xx PCMCIA driver was registering a device_driver with the
    platform_bus_type. Unfortunately, this causes data outside the
    device_driver structure to be dereferenced as if it were a
    platform_driver structure, causing an oops. Convert the PXA2xx
    core driver to use the proper platform_driver structure.

    Signed-off-by: Russell King

    Russell King
     

17 Apr, 2005

1 commit

  • Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds