public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@melbourne.sgi.com>
To: kdb@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: kdb wishlist
Date: Tue, 08 May 2001 22:09:42 +1000	[thread overview]
Message-ID: <23270.989323782@ocs3.ocs-net> (raw)

This is part of my kdb wishlist, does anybody fancy writing the code to
add any of these features?  It would be a nice project for anybody
wanting to start on the kernel.  Replies to kdb@oss.sgi.com please.
Current patches at http://oss.sgi.com/projects/kdb/download/

* Change kdb invocation key from ^A to ^X^X^X within 3 seconds.  ^A is
  used by emacs, bash, minicom etc.

* Command history.  Handle up/down/left/right/delete keys.  Each
  kdba_io routine is responsible for recognising the arch specific
  keys, with a common history and editting routine.

* Clean up repeating commands.  Pressing enter at the kdb prompt
  repeats the previous command, no matter what the previous command
  was.  Some commands it makes no sense to repeat (bp in particular),
  for other commands you want to repeat the command but without the
  parameter (md in particular).

* Embed width and count options in md and mm commands.  Some hardware
  requires that accesses be a specific width, this can be achieved by
  setting BYTESPERWORD but it is awkward.  We want md1 to read one
  byte, md2, md4, md8 commands.  All can have a count field, e.g.
  md1c8 reads 8 bytes one at a time.  mm1, mm2, mm4, mm8 to set memory
  no count field.


             reply	other threads:[~2001-05-08 12:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-08 12:09 Keith Owens [this message]
2001-05-08 12:41 ` kdb wishlist Tigran Aivazian
2001-05-08 15:56 ` george anzinger
2001-05-08 16:57   ` slurn
2001-05-08 17:38     ` Juan Quintela
2001-05-08 18:04       ` slurn
2001-05-08 18:15 ` mirabilos
  -- strict thread matches above, loose matches on Subject: below --
2001-05-08 12:40 r1vamsi
2001-05-08 13:32 Manfred Spraul
2001-05-08 13:36 ` Keith Owens

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=23270.989323782@ocs3.ocs-net \
    --to=kaos@melbourne.sgi.com \
    --cc=kdb@oss.sgi.com \
    --cc=linux-kernel@vger.kernel.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