1. 08 Dec, 2006 3 commits
  2. 16 Nov, 2006 1 commit
  3. 05 Oct, 2006 1 commit
    • David Howells's avatar
      IRQ: Maintain regs pointer globally rather than passing to IRQ handlers · 7d12e780
      David Howells authored
      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
      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:
      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
      Signed-Off-By: default avatarDavid Howells <dhowells@redhat.com>
      (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
  4. 03 Oct, 2006 2 commits
  5. 01 Sep, 2006 1 commit
  6. 30 Aug, 2006 1 commit
  7. 31 Jul, 2006 1 commit
  8. 10 Jul, 2006 1 commit
  9. 02 Jul, 2006 1 commit
  10. 30 Jun, 2006 1 commit
  11. 26 Jun, 2006 3 commits
  12. 25 Jun, 2006 1 commit
  13. 24 Jun, 2006 1 commit
  14. 23 Jun, 2006 1 commit
  15. 11 Apr, 2006 1 commit
  16. 28 Mar, 2006 1 commit
  17. 27 Mar, 2006 2 commits
  18. 14 Jan, 2006 2 commits
  19. 12 Jan, 2006 1 commit
  20. 10 Jan, 2006 12 commits
  21. 05 Jan, 2006 1 commit
    • Luis F. Ortiz's avatar
      [ATYFB]: Fix onboard video on SPARC Blade 100 for 2.6.{13,14,15} · 5b373e10
      Luis F. Ortiz authored
      	I have recently been switching from using 2.4.32 on my trusty
      old Sparc Blade 100 to using 2.6.15 .  Some of the problems I ran into
      were distorted video when the console was active (missing first
      character, skipped dots) and when running X windows (colored snow,
      stripes, missing pixels).  A quick examination of the 2.6 versus 2.4
      source for the ATY driver revealed alot of changes.
               A closer look at the code/data for the 64GR/XL chip revealed
      two minor "typos" that the rewriter(s) of the code made.  The first is
      a incorrect clock value (230 .vs. 235) and the second is a missing
      flag (M64F_SDRAM_MAGIC_PLL).  Making both these changes seems to have
      fixed my problem.  I tend to think the 235 value is the correct one,
      as there is a 29.4 Mhz clock crystal close to the video chip and 235.2
      (29.4*8) is too close to 235 to make it a coincidence.
      	The flag for M64F_SDRAM_MAGIC_PLL was dropped during the
      changes made by adaplas in file revision 1.72 on the old bitkeeper
      	The change relating to the clock rate has been there forever,
      at least in the 2.6 tree.  I'm not sure where to look for the old 2.5
      tree or if anyone cares when it happened.
      On SPARC Blades 100's, which use the ATY MACH64GR video chipset, the
      clock crystal frequency is 235.2 Mhz, not 230 Mhz.  The chipset also
      requires the use of M64F_SDRAM_MAGIC_PLL in order to setup the PLL
      properly for the DRAM.
      Signed-off-by: default avatarLuis F. Ortiz <lfo@Polyad.Org>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  22. 07 Nov, 2005 1 commit
    • Antonino A. Daplas's avatar
      [PATCH] atyfb: Get initial mode timings from LCD BIOS · 1013d266
      Antonino A. Daplas authored
      Reported by: Jean-Philippe Guérard (Bugzilla Bug 1782)
      "I've tried with video=atyfb:debug and video=atyfb:debug,mode:1280x600, \
      In both case, the screen stays black, but seems divided into 4 vertical bands.
       Some white lines pop up randomly on each vertical band."
      The problem is a combination of an incorrect xclk plus lack of timing
      information.  The adapter is attached to an LCD device that can do 1280x600
      (which is not a standard resolution).  The global mode database does not have
      an entry for it.  Fortunately, the Video BIOS contains the complete timing
      info for this display, however, atyfb is not making use of it.
      Add support to get the timing information from the BIOS, if available.
      Signed-off-by: default avatarAntonino Daplas <adaplas@pol.net>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>