1. 22 6月, 2005 5 次提交
    • J
      [PATCH] fbdev: iomove removal · f5a9951c
      James Simmons 提交于
      Since no one is using the inbuf, outbuf of struct fb_pixmap I removed their
      use in the framebuffer console.  The idea is instead move the pixmap
      functionality below the accelerated functions intead of on top as the way
      it is now.  If there is no objection please apply.  This is against Linus
      latestr GIT tree.  Thank you.
      Signed-off-by: NJames Simmons <jsimmons@www.infradead.org>
      Cc: "Antonino A. Daplas" <adaplas@pol.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      f5a9951c
    • A
      [PATCH] intelfbdrv naming fix · 5a3b5899
      Andrew Morton 提交于
      Can't use this fancy name, because it's used to generate a sysfs filename:
      
      kobject_register failed for Intel(R) 830M/845G/852GM/855GM/865G/915G
       Framebuffer Driver (-13)
        [<c01bf8e3>] kobject_register+0x43/0x70
        [<c022dfe2>] bus_add_driver+0x52/0xa0
        [<c01c8c10>] pci_device_shutdown+0x0/0x20
        [<c01c8d71>] pci_register_driver+0x61/0x80
        [<c0387099>] intelfb_init+0x59/0x70
        [<c03787cc>] do_initcalls+0x2c/0xc0
        [<c0159025>] kern_mount+0x15/0x17
        [<c01002a0>] init+0x0/0x100
        [<c01002ca>] init+0x2a/0x100
        [<c0100f58>] kernel_thread_helper+0x0/0x18
        [<c0100f5d>] kernel_thread_helper+0x5/0x18
      
      Cc: "Antonino A. Daplas" <adaplas@pol.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      5a3b5899
    • G
      [PATCH] some vesafb fixes · 78c03717
      Gerd Knorr 提交于
      Fix the size passed to release_mem_region in an error path.
      
      Also adjust the message printed when vesafb cannot load; the comment there
      already says this must not be fatal, so the message should also not mention
      the word 'abort' otherwise indicating a problem to worry about in the log.
      Signed-off-by: NJan Beulich <jbeulich@novell.com>
      Signed-off-by: NGerd Knorr <kraxel@suse.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      78c03717
    • A
      [PATCH] s1d13xxxfb linkage fix · 27f931da
      Andrew Morton 提交于
      s1d13xxxfb_remove() is referenced from s1d13xxxfb_probe(), which is marked
      __devinit().  So s1d13xxxfb_remove() cannot be marked __devexit.
      
      Does this all make sense?  Clearly the __devexit section will still be in
      core when the __devinit code is run, if the driver was loaded as a module.
      
      But I suppose that if the driver is statically linked, the __devexit section
      might be dropped early in boot.  Still, we wouldn't drop __devexit prior to
      initcall completion, at which point the __devinit code has all been run
      anyway.
      
      verdict: this code was legal and made sense.  Is this a generic problem, or an
      arm-specific problem?
      
        UPD     include/linux/compile.h
        CC      init/version.o
        LD      init/built-in.o
        LD      .tmp_vmlinux1
      `.exit.text' referenced in section `.init.text' of drivers/built-in.o: defined in discarded section `.exit.text' of drivers/built-in.o
      
      Cc: Russell King <rmk@arm.linux.org.uk>
      Cc: Rusty Russell <rusty@rustcorp.com.au>
      Cc: Greg KH <greg@kroah.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      27f931da
    • K
      [PATCH] Bring back Tux on Chips 65550 framebuffer · e6afbe59
      Keenan Pepper 提交于
      I don't see any reason why the framebuffer should need to be cleared,
      and it makes Tux vanish.
      
      Cc: <linux-fbdev-devel@lists.sourceforge.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      e6afbe59
  2. 21 6月, 2005 2 次提交
  3. 14 6月, 2005 2 次提交
  4. 13 6月, 2005 1 次提交
  5. 29 5月, 2005 1 次提交
    • P
      [PATCH] intelfb section fix · 346e399b
      Patrick McManus 提交于
      On Nov 16 2004 a change to intelfbdrv.c was commited (as part of 0.9.2 it
      looks like) that added __initdata to all of the module param variables that
      seems to create the opportunity for an oops.
      
      I've recently been chasing an OOPS
      (http://marc.theaimsgroup.com/?l=linux-kernel&m=111552250920370&w=2) I
      created by reading every file on the /sys file system and I've traced it
      back to this code in the intelfbdrv.  Though I had root privs in my initial
      problem report, it turns out they are un-necessary to generate the oops -
      all you've got to do is "cat /sys/module/intelfb/parameters/mode" enough
      times and eventually it will oops.
      
      This is because sysfs automatically exports all module_param declarations
      to the sysfs file system..  which means those variables can be dynamically
      evaluated at any later time, which of course means marking them __initdata
      is a bad idea ;)..  when they happen to be char *'s it is an especially bad
      idea ;).
      
      Applying the patch below clears up the OOPS for me.
      Signed-off-by: NPatrick McManus <mcmanus@ducksong.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      346e399b
  6. 06 5月, 2005 1 次提交
  7. 04 5月, 2005 1 次提交
  8. 03 5月, 2005 1 次提交
  9. 01 5月, 2005 14 次提交
  10. 28 4月, 2005 2 次提交
  11. 26 4月, 2005 2 次提交
  12. 25 4月, 2005 2 次提交
  13. 22 4月, 2005 1 次提交
  14. 17 4月, 2005 3 次提交
    • P
      [PATCH] fix u32 vs. pm_message_t in driver/video · 9bfd354b
      Pavel Machek 提交于
      This fixes u32 vs.  pm_message_t confusion in drivers/video.  Should change no
      code.
      Signed-off-by: NPavel Machek <pavel@suse.cz>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      9bfd354b
    • B
      [PATCH] ppc32: Fix AGP and sleep again · 0c541b44
      Benjamin Herrenschmidt 提交于
      My previous patch that added sleep support for uninorth-agp and some AGP
      "off" stuff in radeonfb and aty128fb is breaking some configs.  More
      specifically, it has problems with rage128 setups since the DRI code for
      these in X doesn't properly re-enable AGP on wakeup or console switch
      (unlike the radeon DRM).
      
      This patch fixes the problem for pmac once for all by using a different
      approach.  The AGP driver "registers" special suspend/resume callbacks with
      some arch code that the fbdev's can later on call to suspend and resume
      AGP, making sure it's resumed back in the same state it was when suspended.
       This is platform specific for now.  It would be too complicated to try to
      do a generic implementation of this at this point due to all sort of weird
      things going on with AGP on other architectures.  We'll re-work that whole
      problem cleanly once we finally merge fbdev's and DRI.
      
      In the meantime, please apply this patch which brings back some r128 based
      laptops into working condition as far as system sleep is concerned.
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      0c541b44
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      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!
      1da177e4