All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Mark Fortescue <mark@mtfhpc.demon.co.uk>
Cc: davem@redhat.com, ecd@skynet.be, jj@sunsite.ms.mff.cuni.cz,
	anton@samba.org, linux-kernel@vger.kernel.org,
	sparclinux@vger.kernel.org, ultralinux@vger.kernel.org,
	trivial@rustcorp.com.au
Subject: Re: PATCH to fix initialisation issue for GC3 (linux-2.5.64 +).
Date: Fri, 29 Oct 2004 00:34:17 +0000	[thread overview]
Message-ID: <20041029003417.GW12934@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10410290107100.1071-100000@mtfhpc.demon.co.uk>

On Fri, Oct 29, 2004 at 01:27:51AM +0100, Mark Fortescue wrote:
> This patch fixes an error in the blanking code for the GCThree SBUS
> video card. Now I get a logo and black screen, not just a blank (no
> video) screen. It is a trivual fix that has taken too long to identify as
> it is such a small typing error during the rewriting of the code for
> the new frame buffer system introduced in the 2.5 series kernels.
> Given that it still exists in the 2.6.8.1 kernel, I assume that not many
> people have tried using the latest kernel on systems with a CGThree.

Yes, all my systems are headless unfortunately.


-- wli

WARNING: multiple messages have this Message-ID (diff)
From: William Lee Irwin III <wli@holomorphy.com>
To: Mark Fortescue <mark@mtfhpc.demon.co.uk>
Cc: davem@redhat.com, ecd@skynet.be, jj@sunsite.ms.mff.cuni.cz,
	anton@samba.org, linux-kernel@vger.kernel.org,
	sparclinux@vger.kernel.org, ultralinux@vger.kernel.org,
	trivial@rustcorp.com.au
Subject: Re: PATCH to fix initialisation issue for GC3 (linux-2.5.64 +).
Date: Thu, 28 Oct 2004 17:34:17 -0700	[thread overview]
Message-ID: <20041029003417.GW12934@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10410290107100.1071-100000@mtfhpc.demon.co.uk>

On Fri, Oct 29, 2004 at 01:27:51AM +0100, Mark Fortescue wrote:
> This patch fixes an error in the blanking code for the GCThree SBUS
> video card. Now I get a logo and black screen, not just a blank (no
> video) screen. It is a trivual fix that has taken too long to identify as
> it is such a small typing error during the rewriting of the code for
> the new frame buffer system introduced in the 2.5 series kernels.
> Given that it still exists in the 2.6.8.1 kernel, I assume that not many
> people have tried using the latest kernel on systems with a CGThree.

Yes, all my systems are headless unfortunately.


-- wli

  reply	other threads:[~2004-10-29  0:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-29  0:27 PATCH to fix initialisation issue for GC3 (linux-2.5.64 +) Mark Fortescue
2004-10-29  0:27 ` Mark Fortescue
2004-10-29  0:34 ` William Lee Irwin III [this message]
2004-10-29  0:34   ` William Lee Irwin III
2004-10-29  3:51   ` Lee Revell
2004-10-29  3:51     ` Lee Revell
2004-10-29  3:55     ` William Lee Irwin III
2004-10-29  3:55       ` William Lee Irwin III
  -- strict thread matches above, loose matches on Subject: below --
2005-02-16 14:15 Meelis Roos
2005-02-16 16:13 ` David S. Miller
2005-02-16 16:27 ` Mark Fortescue

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=20041029003417.GW12934@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=anton@samba.org \
    --cc=davem@redhat.com \
    --cc=ecd@skynet.be \
    --cc=jj@sunsite.ms.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@mtfhpc.demon.co.uk \
    --cc=sparclinux@vger.kernel.org \
    --cc=trivial@rustcorp.com.au \
    --cc=ultralinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.