04 Aug, 2009

2 commits


13 Nov, 2008

2 commits

  • Under qemu there is a race between the TDxE read-and-clear and the SCxTDR
    write. While on hardware it can be gauranteed that the read-and-clear
    will happen prior to the character being written out, no such assumption
    can be made under emulation. As this path happens with IRQs off and the
    hardware itself doesn't care about the ordering, move the SCxTDR write
    until after the read-and-clear.

    Signed-off-by: Vladimir Prus
    Signed-off-by: Paul Mundt

    Paul Mundt
     
  • Add PORT_SCIF to unbreak the early printk code.

    Signed-off-by: Magnus Damm
    Signed-off-by: Paul Mundt

    Magnus Damm
     

08 May, 2008

3 commits


28 Jan, 2008

1 commit


02 Oct, 2007

1 commit

  • setup_early_printk() can be static, and with that, we can kill off
    the early initialization variable and move the CON_BOOT check in
    to the function body.

    Signed-off-by: Paul Mundt

    Paul Mundt
     

21 Sep, 2007

1 commit


17 Aug, 2007

1 commit


09 May, 2007

1 commit

  • The console subsystem already has an idea of a boot console, using the
    CON_BOOT flag. The implementation has some flaws though. The major
    problem is that presence of a boot console makes register_console() ignore
    any other console devices (unless explicitly specified on the kernel
    command line).

    This patch fixes the console selection code to *not* consider a boot
    console a full-featured one, so the first non-boot console registering will
    become the default console instead. This way the unregister call for the
    boot console in the register_console() function actually triggers and the
    handover from the boot console to the real console device works smoothly.
    Added a printk for the handover, so you know which console device the
    output goes to when the boot console stops printing messages.

    The disable_early_printk() call is obsolete with that patch, explicitly
    disabling the early console isn't needed any more as it works automagically
    with that patch.

    I've walked through the tree, dropped all disable_early_printk() instances
    found below arch/ and tagged the consoles with CON_BOOT if needed. The
    code is tested on x86, sh (thanks to Paul) and mips (thanks to Ralf).

    Changes to last version: Rediffed against -rc3, adapted to mips cleanups by
    Ralf, fixed "udbg-immortal" cmd line arg on powerpc.

    Signed-off-by: Gerd Hoffmann
    Acked-by: Paul Mundt
    Acked-by: Ralf Baechle
    Cc: Andi Kleen
    Cc: Alan Cox
    Cc: Richard Henderson
    Cc: Ivan Kokshaysky
    Cc: Paul Mackerras
    Cc: Benjamin Herrenschmidt
    Cc: Jeremy Fitzhardinge
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Gerd Hoffmann
     

13 Feb, 2007

1 commit

  • This allows the baud rate for earlyprintk for sh4 without the
    standard BIOS to be set via the command line. This uses the same
    format as i386 and x86_64, which is:

    earlyprintk=serial,ttySC1,38400

    The second parameter (ttySC1 above) is usually the console device
    name or the io address of the serial port. I allow that to be
    specified but ignore it in order to keep the format the same as
    i386/x86_64.

    Signed-off-by: Jamie Lenehan
    Signed-off-by: Paul Mundt

    Jamie Lenehan
     

12 Dec, 2006

1 commit


06 Dec, 2006

1 commit

  • This makes the early printk support somewhat more flexible,
    moving the port definition to a config option, and making the
    port initialization configurable for sh-ipl+g users.

    At the same time, this allows us to trivially wire up the
    SH7780 SCIF0, so that's thrown in too more or less for free.

    Signed-off-by: Paul Mundt

    Paul Mundt
     

27 Sep, 2006

1 commit

  • Allow multiple early printk consoles via earlyprintk=.

    With this change earlyprintk is no longer enabled by default,
    it must be specified on the kernel command line. Optionally
    with ,keep to prevent unreg by tty_io.

    Signed-off-by: Paul Mundt

    Paul Mundt
     

17 Apr, 2005

1 commit

  • 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!

    Linus Torvalds