1. 20 Jun, 2006 1 commit
  2. 31 Mar, 2006 1 commit
  3. 24 Mar, 2006 1 commit
    • John Z. Bohach's avatar
      [PATCH] console_setup() depends (wrongly?) on CONFIG_PRINTK · 2ea1c539
      John Z. Bohach authored
      
      
      It appears that console_setup() code only gets compiled into the kernel if
      CONFIG_PRINTK is enabled.  One detrimental side-effect of this is that
      serial8250_console_setup() never gets invoked when CONFIG_PRINTK is not
      set, resulting in baud rate not being read/parsed from command line (i.e.
      console=ttyS0,115200n8 is ignored, at least the baud rate part...)
      
      Attached patch moves console_setup() code from inside
      
      #ifdef CONFIG_PRINTK
      
      to outside (in printk.c), removing dependence on said config. option.
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      2ea1c539
  4. 15 Jan, 2006 1 commit
  5. 09 Jan, 2006 1 commit
  6. 24 Nov, 2005 1 commit
  7. 14 Nov, 2005 1 commit
  8. 07 Nov, 2005 1 commit
  9. 31 Oct, 2005 1 commit
  10. 21 Sep, 2005 1 commit
    • Andrew Morton's avatar
      [PATCH] Add printk_clock() · 31f6d9d6
      Andrew Morton authored
      
      
      ia64's sched_clock() accesses per-cpu data which isn't set up at boot time.
      Hence ia64 cannot use printk timestamping, because printk() will crash in
      sched_clock().
      
      So make printk() use printk_clock(), defaulting to sched_clock(), overrideable
      by the architecture via attribute(weak).
      
      Cc: "Luck, Tony" <tony.luck@intel.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      31f6d9d6
  11. 07 Sep, 2005 1 commit
  12. 25 Jun, 2005 1 commit
    • Shaohua Li's avatar
      [PATCH] CPU hotplug printk fix · ac255752
      Shaohua Li authored
      
      
      In the cpu hotplug case, per-cpu data possibly isn't initialized even the
      system state is 'running'.  As the comments say in the original code, some
      console drivers assume per-cpu resources have been allocated.  radeon fb is
      one such driver, which uses kmalloc.  After a CPU is down, the per-cpu data
      of slab is freed, so the system crashed when printing some info.
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      ac255752
  13. 23 Jun, 2005 1 commit
    • Greg Edwards's avatar
      [PATCH] CON_CONSDEV bit not set correctly on last console · ab4af03a
      Greg Edwards authored
      
      
      According to include/linux/console.h, CON_CONSDEV flag should be set on
      the last console specified on the boot command line:
      
           86 #define CON_PRINTBUFFER (1)
           87 #define CON_CONSDEV     (2) /* Last on the command line */
           88 #define CON_ENABLED     (4)
           89 #define CON_BOOT        (8)
      
      This does not currently happen if there is more than one console specified
      on the boot commandline.  Instead, it gets set on the first console on the
      command line.  This can cause problems for things like kdb that look for
      the CON_CONSDEV flag to see if the console is valid.
      
      Additionaly, it doesn't look like CON_CONSDEV is reassigned to the next
      preferred console at unregister time if the console being unregistered
      currently has that bit set.
      
      Example (from sn2 ia64):
      
      elilo vmlinuz root=<dev> console=ttyS0 console=ttySG0
      
      in this case, the flags on ttySG console struct will be 0x4 (should be
      0x6).
      
      Attached patch against bk fixes both issues for the cases I looked at.  It
      uses selected_console (which gets incremented for each console specified on
      the command line) as the indicator of which console to set CON_CONSDEV on.
      When adding the console to the list, if the previous one had CON_CONSDEV
      set, it masks it out.  Tested on ia64 and x86.
      
      The problem with the current behavior is it breaks overriding the default from
      the boot line.  In the ia64 case, there may be a global append line defining
      console=a in elilo.conf.  Then you want to boot your kernel, and want to
      override the default by passing console=b on the boot line.  elilo constructs
      the kernel cmdline by starting with the value of the global append line, then
      tacks on whatever else you specify, which puts console=b last.
      Signed-off-by: default avatarGreg Edwards <edwardsg@sgi.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      ab4af03a
  14. 17 May, 2005 1 commit
  15. 01 May, 2005 1 commit
  16. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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