17 Mar, 2009

1 commit

  • With arch/sh/drivers/dma/ always being built, the Dreamcast DMA engines
    are being unconditionally built in, regardless of whether the DMA API is
    enabled or not. This is a regression from previous behaviour, but there
    is not much advantage in building them all in unconditionally regardless.
    Add a new config option to make it optional, and update the only user of
    it to reflect that.

    Signed-off-by: Paul Mundt

    Paul Mundt
     

29 Jul, 2008

1 commit


06 Mar, 2008

1 commit

  • Building with CONFIG_DEBUG_SECTION_MISMATCH=y reports:

    CC drivers/video/pvr2fb.o
    LD drivers/video/built-in.o
    WARNING: drivers/video/built-in.o(.text+0xb9b0): Section mismatch in reference from the function pvr2fb_check_var() to the variable .devinit.data:pvr2_fix
    The function pvr2fb_check_var() references
    the variable __devinitdata pvr2_fix.
    This is often because pvr2fb_check_var lacks a __devinitdata
    annotation or the annotation of pvr2_fix is wrong.

    This is obviously crap as no such reference exists, but it's a bit
    closer to reality from older versions which blamed the PCI table. The
    real problem was a reference to pvr2_var.vmode from pvr2fb_check_var(),
    as pvr2_var is flagged as __devinitdata (pvr2_fix is also, so at least
    that part is right).

    pvr2_var.vmode is just a fancy way of saying FB_VMODE_NONINTERLACED, so
    we just reference that explicitly instead.

    Signed-off-by: Paul Mundt

    Paul Mundt
     

17 Oct, 2007

1 commit


01 Oct, 2007

1 commit


21 Sep, 2007

1 commit

  • The maple bus driver (http://lkml.org/lkml/2007/9/4/165) uses hardware
    synchronisation between the maple bus and the VBLANK to poll the maple
    bus. This patch makes the interrupt shareable.

    By definition the interrupt is for both devices.

    Signed-off by: Adrian McMenamin
    Signed-off-by: Paul Mundt

    Adrian McMenamin
     

12 Aug, 2007

2 commits

  • - better handling of the pvr2 registers based on more up to date information.

    Testing shows that it seems to work pretty well at 16bpp, 24bpp and 32bpp -
    including proper rendering of the boot logo at all levels (previously this was
    a bit broken even at 16bpp) and giving white against black text. Really
    detailed testing (eg with X11) requires support for the maple bus - which
    isn't (currently - next project assuming this is okay) available, but I have
    no reason to think this is broken.

    Signed-off by: Adrian McMenamin
    Acked-by: Paul Mundt
    Signed-off-by: Antonino Daplas
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Adrian McMenamin
     
  • Reported by: Adrian McMenamin

    This driver will oops when the pseudo_palette[] is written as u32 but not when
    written as u16. When written as u32, it corrupts the adjacent 'mmio_base'
    field of struct pvr2fb_par. Fix by using framebuffer_alloc()/release() to
    allocate struct fb_info and struct pvr2fb_par, and create the pseudo_palette[]
    as part of struct pvr2fb_par.

    Signed-off-by: Antonino Daplas
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Antonino A. Daplas
     

20 Jul, 2007

1 commit

  • Transform some calls to kmalloc/memset to a single kzalloc (or kcalloc).

    Here is a short excerpt of the semantic patch performing
    this transformation:

    @@
    type T2;
    expression x;
    identifier f,fld;
    expression E;
    expression E1,E2;
    expression e1,e2,e3,y;
    statement S;
    @@

    x =
    - kmalloc
    + kzalloc
    (E1,E2)
    ... when != \(x->fld=E;\|y=f(...,x,...);\|f(...,x,...);\|x=E;\|while(...) S\|for(e1;e2;e3) S\)
    - memset((T2)x,0,E1);

    @@
    expression E1,E2,E3;
    @@

    - kzalloc(E1 * E2,E3)
    + kcalloc(E1,E2,E3)

    [akpm@linux-foundation.org: get kcalloc args the right way around]
    Signed-off-by: Yoann Padioleau
    Cc: Richard Henderson
    Cc: Ivan Kokshaysky
    Acked-by: Russell King
    Cc: Bryan Wu
    Acked-by: Jiri Slaby
    Cc: Dave Airlie
    Acked-by: Roland Dreier
    Cc: Jiri Kosina
    Acked-by: Dmitry Torokhov
    Cc: Benjamin Herrenschmidt
    Acked-by: Mauro Carvalho Chehab
    Acked-by: Pierre Ossman
    Cc: Jeff Garzik
    Cc: "David S. Miller"
    Acked-by: Greg KH
    Cc: James Bottomley
    Cc: "Antonino A. Daplas"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Yoann Padioleau
     

18 Jul, 2007

1 commit


07 Jul, 2007

2 commits

  • In the PCI + hotplug case we end up with some bogus references between
    the PCI driver path and the DC path. In order to fix this, we have to
    rework the common init path for __devinit, as well as moving all of the
    data that it references to __devinidata.

    Signed-off-by: Paul Mundt

    Paul Mundt
     
  • A few minor things were broken here. fix and var screeninfo should have
    been __devinitdata, board_list[] gets renamed to board_driver[] so the
    modpost matching does the right thing, and we properly discard some of
    the unused exit sections.

    Signed-off-by: Paul Mundt

    Paul Mundt
     

09 May, 2007

1 commit


09 Dec, 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
     

27 Sep, 2006

1 commit


11 Jul, 2006

1 commit

  • MAX_NR_CONSOLES, fg_console, want_console and last_console are more of a
    function of the VT layer than the TTY one. Moving these to vt.h and vt_kern.h
    allows all of the framebuffer and VT console drivers to remove their
    dependency on tty.h.

    [akpm@osdl.org: fix alpha build]
    Signed-off-by: Jon Smirl
    Signed-off-by: Antonino Daplas
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jon Smirl
     

01 Jul, 2006

1 commit


07 Nov, 2005

1 commit

  • According to Jon Smirl, filling in the field fb_cursor with soft_cursor for
    drivers that do not support hardware cursors is redundant. The soft_cursor
    function is usable by all drivers because it is just a wrapper around
    fb_imageblit. And because soft_cursor is an fbcon-specific hook, the file is
    moved to the console directory.

    Thus, drivers that do not support hardware cursors can leave the fb_cursor
    field blank. For drivers that do, they can fill up this field with their own
    version.

    The end result is a smaller code size. And if the framebuffer console is not
    loaded, module/kernel size is also reduced because the soft_cursor module will
    also not be loaded.

    Signed-off-by: Antonino Daplas
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Antonino A. Daplas
     

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