public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, p_gortmaker@yahoo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] omission in video driver
Date: Wed, 3 Apr 2002 22:51:31 GMT	[thread overview]
Message-ID: <UTC200204032251.WAA510106.aeb@cwi.nl> (raw)

: Heh, you mean "here is the hardware information, please make a patch".
: But your choice of red makes it truly a "bleeding edge" kernel :)

: The fact that we have been using linux for ~ 10 yrs and nobody has
: complained about the lack of this function yet says something...

: Anyway, have a look at this and see if it is what you had in mind.
: I figured it would be sensible to have a per VC colour

Yes, bleeding edge it was.

Adding something like this is allowed only on April 1st.

[But other systems have it. I find that both FreeBSD and UnixWare
have a KDSBORDER ioctl.]

Yes, your patch sounds more or less OK, but more less than more,
since I think that this should be treated completely parallel
to the palette stuff. And that works as follows:
There are ioctls and escape sequences. Escape sequences set
the palette per-VC. Upon reset the palette is reset to a default.
The default is set by ioctl. (And at the moment the ioctl sets
the default, it is also applied to the actual screen.)

[Not that I like this construction so much, but for uniformity..]
[In fact the author of the palette patch did not know the standard
for escape sequences, but nobody stopped him.]

Andries

             reply	other threads:[~2002-04-03 22:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-03 22:51 Andries.Brouwer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-04 13:13 [PATCH] omission in video driver Andries.Brouwer
2002-04-01 18:41 Andries.Brouwer
2002-04-03 13:27 ` Paul Gortmaker

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=UTC200204032251.WAA510106.aeb@cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p_gortmaker@yahoo.com \
    /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