1. 12 10月, 2007 1 次提交
  2. 18 7月, 2007 1 次提交
    • M
      sb1250-duart.c: SB1250 DUART serial support · b45d5279
      Maciej W. Rozycki 提交于
      This is a driver for the SB1250 DUART, a dual serial port implementation
      included in the Broadcom family of SOCs descending from the SiByte SB1250
      MIPS64 chip multiprocessor.  It is a new implementation replacing the
      old-fashioned driver currently present in the linux-mips.org tree.  It
      supports all the usual features one would expect from a(n asynchronous)
      serial driver, including modem line control (as far as hardware supports it
      -- there is edge detection logic missing from the DCD and RI lines and the
      driver does not implement polling of these lines at the moment), the serial
      console, BREAK transmission and reception, including the magic SysRq.  The
      receive FIFO threshold is not maintained though.
      
      The driver was tested with a SWARM board which uses a BCM1250 SOC (which is
      dual MIPS64 CMP) and has both ports of the single DUART implemented wired
      externally.  Both were tested.  Testing included using the ports as
      terminal lines at 1200bps (which is the ports minimum), 115200bps and a
      couple of random speeds inbetween.  The modem lines were verified to
      operate correctly.  No testing was performed with a use as a network
      interface, like with SLIP or PPP.
      Signed-off-by: NMaciej W. Rozycki <macro@linux-mips.org>
      Acked-by: NRalf Baechle <ralf@linux-mips.org>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      b45d5279
  3. 20 4月, 2007 1 次提交
  4. 10 3月, 2007 1 次提交
  5. 05 3月, 2007 1 次提交
  6. 01 7月, 2006 1 次提交
  7. 07 2月, 2006 2 次提交
  8. 30 10月, 2005 1 次提交
  9. 17 4月, 2005 1 次提交
    • 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