1. 26 Aug, 2007 1 commit
  2. 11 Aug, 2007 5 commits
  3. 03 Aug, 2007 1 commit
  4. 31 Jul, 2007 8 commits
  5. 30 Jul, 2007 2 commits
    • David S. Miller's avatar
      [SPARC]: Mark SBUS framebuffer ioctls as IGNORE in compat_ioctl.c · 8163904e
      David S. Miller authored
      
      
      They are handled in a ->compat_ioctl() handler, so it's just noise
      when compat_ioctl.c warns which occurs when they are used on non-SBUS
      framebuffer devices.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      8163904e
    • David S. Miller's avatar
      [VIDEO]: Fix OOPS in all SBUS framebuffer drivers. · c7f439b9
      David S. Miller authored
      
      
      All of these drivers use a silly:
      
      struct all_info {
      	struct fb_info info;
      	struct foo_par par;
      };
      
      struct all_info *all = kzalloc(sizeof(*all), GFP_KERNEL);
      all->info.par = &all->par;
      
      etc. etc. code sequence, basically replicating the provided
      framebuffer_alloc()/framebuffer_release(), and doing it badly.
      
      Not only is this massive code duplication, it also caused a
      bug in that we weren't setting the fb_info->device pointer
      which results in an OOPS when fb_is_primary_device() runs.
      
      Fix all of this by using framebuffer_{alloc,release}() and
      passing in "&of_device->dev" as the device pointer.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      c7f439b9
  6. 26 Jul, 2007 2 commits
  7. 24 Jul, 2007 1 commit
  8. 22 Jul, 2007 1 commit
  9. 21 Jul, 2007 7 commits
  10. 20 Jul, 2007 2 commits
    • David S. Miller's avatar
      [SPARC]: Fix serial console device detection. · c73fcc84
      David S. Miller authored
      
      
      The current scheme works on static interpretation of text names, which
      is wrong.
      
      The output-device setting, for example, must be resolved via an alias
      or similar to a full path name to the console device.
      
      Paths also contain an optional set of 'options', which starts with a
      colon at the end of the path.  The option area is used to specify
      which of two serial ports ('a' or 'b') the path refers to when a
      device node drives multiple ports.  'a' is assumed if the option
      specification is missing.
      
      This was caught by the UltraSPARC-T1 simulator.  The 'output-device'
      property was set to 'ttya' and we didn't pick upon the fact that this
      is an OBP alias set to '/virtual-devices/console'.  Instead we saw it
      as the first serial console device, instead of the hypervisor console.
      
      The infrastructure is now there to take advantage of this to resolve
      the console correctly even in multi-head situations in fbcon too.
      
      Thanks to Greg Onufer for the bug report.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      c73fcc84
    • Jesper Juhl's avatar
      cr_backlight_probe() allocates too little storage for struct cr_panel · e3bbb3f0
      Jesper Juhl authored
      
      
      The Coverity checker noticed that we allocate too little storage for
      "struct cr_panel *crp" in cr_backlight_probe().
      Signed-off-by: default avatarJesper Juhl <jesper.juhl@gmail.com>
      Cc: Thomas Hellstrom <thomas@tungstengraphics.com>
      Cc: Alan Hourihane <alanh@tungstengraphics.com>
      Cc: <stable@kernel.org>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      e3bbb3f0
  11. 19 Jul, 2007 1 commit
  12. 18 Jul, 2007 1 commit
  13. 17 Jul, 2007 8 commits