qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bryce Lanham <blanham@gmail.com>
To: qemu-devel@nongnu.org
Cc: Bryce Lanham <blanham@gmail.com>
Subject: [Qemu-devel] [PATCH 0/8] *** SUBJECT HERE ***
Date: Wed, 17 Aug 2011 17:09:04 -0500	[thread overview]
Message-ID: <1313618952-14774-2-git-send-email-blanham@gmail.com> (raw)
In-Reply-To: <1313618952-14774-1-git-send-email-blanham@gmail.com>

*** BLURB HERE ***

Bryce Lanham (8):
  added next source files to Makefile.target
  main next driver, needs a bit of cleanup
  next framebuffer driver, very basic, only supports running under 32
    bit color at the moment
  next keyboard driver, only supports a subset of modifier keys
  partially working network driver, needs more comparison with real
    hardware before it can be made fully working
  adds SFC, DFC, MMU TC, access control register, and user stack
    pointer acces to movec_to/from
  added move16, cinva, pflush instructions, and disabled abort on
    execution of frestore/fsave
  added mmu tc, sfc, dfc, and access control registers to the cpu
    header

 Makefile.target         |    2 +
 hw/next-cube.c          |  471 +++++++++++++++++++++++++++++++++++++++++++
 hw/next-fb.c            |  102 ++++++++++
 hw/next-fb.h            |   14 ++
 hw/next-kbd.c           |  243 ++++++++++++++++++++++
 hw/next-kbd.h           |    2 +
 hw/next-net.c           |  513 +++++++++++++++++++++++++++++++++++++++++++++++
 hw/next-net.h           |    2 +
 target-m68k/cpu.h       |   12 +-
 target-m68k/helper.c    |   44 ++++-
 target-m68k/translate.c |  108 +++++++++-
 11 files changed, 1491 insertions(+), 22 deletions(-)
 create mode 100644 hw/next-cube.c
 create mode 100644 hw/next-fb.c
 create mode 100644 hw/next-fb.h
 create mode 100644 hw/next-kbd.c
 create mode 100644 hw/next-kbd.h
 create mode 100644 hw/next-net.c
 create mode 100644 hw/next-net.h

-- 
1.7.2.3

  reply	other threads:[~2011-08-17 22:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-17 22:09 [Qemu-devel] [RFC][PATCH 0/8] NeXT black hardware support Bryce Lanham
2011-08-17 22:09 ` Bryce Lanham [this message]
2011-08-19 13:19   ` [Qemu-devel] [PATCH 0/8] *** SUBJECT HERE *** Laurent Vivier
2011-08-17 22:09 ` [Qemu-devel] [PATCH 1/8] added next source files to Makefile.target Bryce Lanham
2011-08-21 22:31   ` Andreas Färber
2011-08-17 22:09 ` [Qemu-devel] [PATCH 2/8] main next driver, needs a bit of cleanup Bryce Lanham
2011-08-17 22:09 ` [Qemu-devel] [PATCH 3/8] next framebuffer driver, very basic, only supports running under 32 bit color at the moment Bryce Lanham
2011-08-17 22:09 ` [Qemu-devel] [PATCH 4/8] next keyboard driver, only supports a subset of modifier keys Bryce Lanham
2011-08-17 22:09 ` [Qemu-devel] [PATCH 5/8] partially working network driver, needs more comparison with real hardware before it can be made fully working Bryce Lanham
2011-08-17 22:09 ` [Qemu-devel] [PATCH 6/8] adds SFC, DFC, MMU TC, access control register, and user stack pointer acces to movec_to/from Bryce Lanham
2011-08-17 22:09 ` [Qemu-devel] [PATCH 7/8] added move16, cinva, pflush instructions, and disabled abort on execution of frestore/fsave Bryce Lanham
2011-08-17 22:09 ` [Qemu-devel] [PATCH 8/8] added mmu tc, sfc, dfc, and access control registers to the cpu header Bryce Lanham

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1313618952-14774-2-git-send-email-blanham@gmail.com \
    --to=blanham@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).