From: William Lee Irwin III <wli@holomorphy.com>
To: Mark Fortescue <mark@mtfhpc.demon.co.uk>
Cc: linux-fbdev-devel@lists.sourceforge.net, jsimmons@infradead.org,
geert@linux-m68k.org, sparclinux@vger.kernel.org,
ultralinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Help re Frame Buffer/Console Problems
Date: Fri, 29 Oct 2004 11:27:28 -0700 [thread overview]
Message-ID: <20041029182728.GE12934@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10410291849480.2831-100000@mtfhpc.demon.co.uk>
On Fri, Oct 29, 2004 at 07:22:11PM +0100, Mark Fortescue wrote:
> I have been trying to get a CG3 sparc clone up and running with linux.
> Under 2.2.26, the console is fine. During the development of the
> 2.5.x/2.6.x frame buffer system the CG3 support got broken. I have managed
> to track done one of the problems (the blanking code had some typing
> errors in it) and this gave me a logo + black screen and cursor using a
> linux-2.2.8.1 kernel. Still no console text.
> Given that 2.2.10-rc1-bk6 is available, I have downloaded and applied the
> appropriate patches and made some additional mods to keep the
> compiler/linker happy. Now I have a black console, no text, logo or cursor
> and if I redirect the console output to a serial port I get the following:
Okay, sounds like a relatively major disaster. =(
-- 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: linux-fbdev-devel@lists.sourceforge.net, jsimmons@infradead.org,
geert@linux-m68k.org, sparclinux@vger.kernel.org,
ultralinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Help re Frame Buffer/Console Problems
Date: Fri, 29 Oct 2004 18:27:28 +0000 [thread overview]
Message-ID: <20041029182728.GE12934@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10410291849480.2831-100000@mtfhpc.demon.co.uk>
On Fri, Oct 29, 2004 at 07:22:11PM +0100, Mark Fortescue wrote:
> I have been trying to get a CG3 sparc clone up and running with linux.
> Under 2.2.26, the console is fine. During the development of the
> 2.5.x/2.6.x frame buffer system the CG3 support got broken. I have managed
> to track done one of the problems (the blanking code had some typing
> errors in it) and this gave me a logo + black screen and cursor using a
> linux-2.2.8.1 kernel. Still no console text.
> Given that 2.2.10-rc1-bk6 is available, I have downloaded and applied the
> appropriate patches and made some additional mods to keep the
> compiler/linker happy. Now I have a black console, no text, logo or cursor
> and if I redirect the console output to a serial port I get the following:
Okay, sounds like a relatively major disaster. =(
-- wli
next prev parent reply other threads:[~2004-10-29 18:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 18:22 Help re Frame Buffer/Console Problems Mark Fortescue
2004-10-29 18:22 ` Mark Fortescue
2004-10-29 18:27 ` William Lee Irwin III [this message]
2004-10-29 18:27 ` William Lee Irwin III
2004-10-29 20:29 ` SPARC argument passing bug in sd.c Keith M Wesolowski
2004-10-29 20:29 ` Keith M Wesolowski
2004-10-30 0:25 ` [Linux-fbdev-devel] Help re Frame Buffer/Console Problems Antonino A. Daplas
2004-10-30 0:25 ` Antonino A. Daplas
2004-11-01 17:32 ` Mark Fortescue
2004-11-01 17:32 ` Mark Fortescue
2004-11-01 23:46 ` Antonino A. Daplas
2004-11-01 23:46 ` Antonino A. Daplas
2004-11-01 23:46 ` Antonino A. Daplas
2004-11-01 23:46 ` Antonino A. Daplas
2004-11-02 0:26 ` Helge Deller
2004-11-02 0:26 ` Helge Deller
2004-11-02 14:26 ` Mark Fortescue
2004-11-02 14:26 ` Mark Fortescue
2004-11-02 14:26 ` Mark Fortescue
2004-11-02 18:03 ` Mark Fortescue
2004-11-02 18:03 ` Mark Fortescue
2004-11-02 18:03 ` Mark Fortescue
2004-11-02 21:40 ` Antonino A. Daplas
2004-11-02 21:40 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-11-02 21:40 ` Antonino A. Daplas
2004-11-02 21:40 ` Antonino A. Daplas
2004-11-02 22:57 ` Mark Fortescue
2004-11-02 22:57 ` Mark Fortescue
2004-11-02 22:57 ` Mark Fortescue
2004-11-02 23:19 ` Antonino A. Daplas
2004-11-02 23:19 ` Antonino A. Daplas
2004-11-03 0:01 ` Mark Fortescue
2004-11-03 0:01 ` Mark Fortescue
2004-11-03 0:01 ` 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=20041029182728.GE12934@holomorphy.com \
--to=wli@holomorphy.com \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mtfhpc.demon.co.uk \
--cc=sparclinux@vger.kernel.org \
--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.