11 Oct, 2007

4 commits


26 Apr, 2007

2 commits


12 Jan, 2007

1 commit

  • Setting .ConfigBase and .Present is now done at the pcmcia core.

    The driver cleanup missed a few places where the driver did set .Present
    to PRESENT_OPTION and later to the values from the CIS. Setting to
    PRESENT_OPTION now overrides the values from the CIS. So just remove
    those lines.

    Signed-off-by: Daniel Ritz
    Signed-off-by: Dominik Brodowski
    Signed-off-by: Linus Torvalds

    Daniel Ritz
     

05 Dec, 2006

2 commits

  • struct pcmcia_device *p_dev->conf.ConfigBase and .Present are set in almost
    all PCMICA driver right at the beginning, using the same calls but slightly
    different implementations. Unfiy this in the PCMCIA core.

    Includes a small bugfix ("drivers/net/pcmcia/xirc2ps_cs.c: remove unused
    label") from and Signed-off-by Adrian Bunk

    Signed-off-by: Dominik Brodowski

    Dominik Brodowski
     
  • As we read out the product information strings (VERS_1) from the PCMCIA device
    in the PCMCIA core, and device drivers can access those reliably in struct
    pcmcia_device's fields prod_id[], remove additional product information string
    detection logic from PCMCIA device drivers.

    Signed-off-by: Dominik Brodowski

    Dominik Brodowski
     

17 Oct, 2006

1 commit


05 Oct, 2006

1 commit

  • Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
    of passing regs around manually through all ~1800 interrupt handlers in the
    Linux kernel.

    The regs pointer is used in few places, but it potentially costs both stack
    space and code to pass it around. On the FRV arch, removing the regs parameter
    from all the genirq function results in a 20% speed up of the IRQ exit path
    (ie: from leaving timer_interrupt() to leaving do_IRQ()).

    Where appropriate, an arch may override the generic storage facility and do
    something different with the variable. On FRV, for instance, the address is
    maintained in GR28 at all times inside the kernel as part of general exception
    handling.

    Having looked over the code, it appears that the parameter may be handed down
    through up to twenty or so layers of functions. Consider a USB character
    device attached to a USB hub, attached to a USB controller that posts its
    interrupts through a cascaded auxiliary interrupt controller. A character
    device driver may want to pass regs to the sysrq handler through the input
    layer which adds another few layers of parameter passing.

    I've build this code with allyesconfig for x86_64 and i386. I've runtested the
    main part of the code on FRV and i386, though I can't test most of the drivers.
    I've also done partial conversion for powerpc and MIPS - these at least compile
    with minimal configurations.

    This will affect all archs. Mostly the changes should be relatively easy.
    Take do_IRQ(), store the regs pointer at the beginning, saving the old one:

    struct pt_regs *old_regs = set_irq_regs(regs);

    And put the old one back at the end:

    set_irq_regs(old_regs);

    Don't pass regs through to generic_handle_irq() or __do_IRQ().

    In timer_interrupt(), this sort of change will be necessary:

    - update_process_times(user_mode(regs));
    - profile_tick(CPU_PROFILING, regs);
    + update_process_times(user_mode(get_irq_regs()));
    + profile_tick(CPU_PROFILING);

    I'd like to move update_process_times()'s use of get_irq_regs() into itself,
    except that i386, alone of the archs, uses something other than user_mode().

    Some notes on the interrupt handling in the drivers:

    (*) input_dev() is now gone entirely. The regs pointer is no longer stored in
    the input_dev struct.

    (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking. It does
    something different depending on whether it's been supplied with a regs
    pointer or not.

    (*) Various IRQ handler function pointers have been moved to type
    irq_handler_t.

    Signed-Off-By: David Howells
    (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)

    David Howells
     

26 Sep, 2006

1 commit


14 Sep, 2006

1 commit


15 Aug, 2006

1 commit


01 Jul, 2006

1 commit


23 Jun, 2006

1 commit

  • First of all it is unnecessary to allocate a new skb in skb_pad since
    the existing one is not shared. More importantly, our hard_start_xmit
    interface does not allow a new skb to be allocated since that breaks
    requeueing.

    This patch uses pskb_expand_head to expand the existing skb and linearize
    it if needed. Actually, someone should sift through every instance of
    skb_pad on a non-linear skb as they do not fit the reasons why this was
    originally created.

    Incidentally, this fixes a minor bug when the skb is cloned (tcpdump,
    TCP, etc.). As it is skb_pad will simply write over a cloned skb. Because
    of the position of the write it is unlikely to cause problems but still
    it's best if we don't do it.

    Signed-off-by: Herbert Xu
    Signed-off-by: David S. Miller

    Herbert Xu
     

31 Mar, 2006

9 commits


17 Jan, 2006

1 commit

  • ESSIDs can technically include NULL characters. Drivers should not be
    adjusting the length of the ESSID before reporting it in their
    SIOCGIWESSID handlers. Breaks stuff like wpa_supplicant. Note that ipw
    drivers, which seem to currently be the "most correct", don't have this
    problem.

    Signed-off-by: Dan Williams
    Signed-off-by: John W. Linville

    Dan Williams
     

06 Jan, 2006

3 commits

  • Unify the EVENT_CARD_INSERTION and "attach" callbacks to one unified
    probe() callback. As all in-kernel drivers are changed to this new
    callback, there will be no temporary backwards-compatibility. Inside a
    probe() function, each driver _must_ set struct pcmcia_device
    *p_dev->instance and instance->handle correctly.

    With these patches, the basic driver interface for 16-bit PCMCIA drivers
    now has the classic four callbacks known also from other buses:

    int (*probe) (struct pcmcia_device *dev);
    void (*remove) (struct pcmcia_device *dev);

    int (*suspend) (struct pcmcia_device *dev);
    int (*resume) (struct pcmcia_device *dev);

    Signed-off-by: Dominik Brodowski

    Dominik Brodowski
     
  • Unify the "detach" and REMOVAL_EVENT handlers to one "remove" function.
    Old functionality is preserved, for the moment.

    Signed-off-by: Dominik Brodowski

    Dominik Brodowski
     
  • Move the suspend and resume methods out of the event handler, and into
    special functions. Also use these functions for pre- and post-reset, as
    almost all drivers already do, and the remaining ones can easily be
    converted.

    Bugfix to include/pcmcia/ds.c
    Signed-off-by: Andrew Morton

    Signed-off-by: Dominik Brodowski

    Dominik Brodowski
     

14 Sep, 2005

1 commit


07 Sep, 2005

2 commits


08 Jul, 2005

2 commits


28 Jun, 2005

1 commit


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