1. 16 8月, 2005 4 次提交
    • A
      [PATCH] intelfb/fbdev: Save info->flags in a local variable · 3edea483
      Antonino A. Daplas 提交于
      Reported by: Pavel Kysilka (Bugzilla Bug 5059)
      
      The intelfb driver does not keep resolution set with fbset after
      switching to anot console and back.
      
      Steps to reproduce:
      
        initial options: tty1,tty2 - 1024x768-60
        1) tty1 - fbset after booting (1024x768-60)
        2) tty1 - fbset 800x600-100
        tty1: 800x600-100
        3) swith to tty2, swith to tty1
        tty1: 1024x768-60 (the same resolution as default from kernel booting)
      
      This bug is caused by intelfb unintentionally destroying info->flags in
      set_par(). Therefore the flag, FBINFO_MISC_USEREVENT used to notify
      fbcon of a mode change was cleared causing the above problem. This bug
      though is not intelfb specific, as other drivers may also be affected.
      
      The fix is to save info->flags in a local variable before calling any
      of the driver hooks.  A more definitive fix (for post 2.6.13) is to
      separate info->flags into one that is set by the driver and another that
      is set by core fbdev/fbcon.
      Signed-off-by: NAntonino Daplas <adaplas@pol.net>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      3edea483
    • S
      [PATCH] intelfb: Do not ioremap entire graphics aperture · 6bd49341
      Sylvain Meyer 提交于
      Reported by: Pavel Kysilka (Bugzilla Bug 4738)
      
      modprobe of intelfb results in the following error message:
      
      	intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G chi
      	intelfb: Version 0.9.2
      	ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16
      	allocation failed: out of vmalloc space - use vmalloc=<size> to increase siz
      	intelfb: Cannot remap FB region.
      
      This will fail if the graphics aperture size is greater than 128 MB.
      
      Fix is to ioremap only from the beginning of graphics aperture to the
      end of the used framebuffer memory.
      Signed-off-by: NSylvain Meyer <sylvain.meyer@worldonline.fr>
      Signed-off-by: NAntonino Daplas <adaplas@pol.net>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      6bd49341
    • J
      [PATCH] inotify: add MOVE_SELF event · 89204c40
      John McCutchan 提交于
      This adds a MOVE_SELF event to inotify.  It is sent whenever the inode
      you are watching is moved.  We need this event so that we can catch
      something like this:
      
       - app1:
      	watch /etc/mtab
      
       - app2:
      	cp /etc/mtab /tmp/mtab-work
      	mv /etc/mtab /etc/mtab~
      	mv /tmp/mtab-work /etc/mtab
      
      app1 still thinks it's watching /etc/mtab but it's actually watching
      /etc/mtab~.
      Signed-off-by: NJohn McCutchan <ttb@tentacle.dhs.org>
      Signed-off-by: NRobert Love <rml@novell.com>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      89204c40
    • R
      [PATCH] inotify: fix idr_get_new_above usage · 0bf955ce
      Robert Love 提交于
      We are saving the wrong thing in ->last_wd.  We want the wd, not the
      return value.
      Signed-off-by: NRobert Love <rml@novell.com>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      0bf955ce
  2. 15 8月, 2005 4 次提交
  3. 14 8月, 2005 3 次提交
  4. 13 8月, 2005 3 次提交
  5. 12 8月, 2005 10 次提交
  6. 11 8月, 2005 14 次提交
  7. 10 8月, 2005 2 次提交