linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Cox <adrian@humboldt.co.uk>
To: Dieu Morales <dieumorales@yahoo.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Asiliantfb (Frame Buffer) Driver
Date: Tue, 22 Jun 2004 08:05:51 +0100	[thread overview]
Message-ID: <1087887950.1547.98.camel@newt> (raw)
In-Reply-To: <20040621212131.61159.qmail@web60405.mail.yahoo.com>


On Mon, 2004-06-21 at 22:21, Dieu Morales wrote:
> My firmware does initialize the CT69000 as an
> environment option that allows what looks like VGA
> mode consisting of a simple black screen with
> white text.  As per some suggestions I have removed
> vga_con and added fb_con but received different(worse)
> results.  Without conswitchp = &fb_con I get an
> exception shortly after the asiliant driver has been
> initialized. And with conswitchp = &fb_con the system
> hangs immediately after ppc.md.setup_arch in setup.c.

What I do is to have this in my platform setup code:

#ifdef CONFIG_DUMMY_CONSOLE
	conswitchp = &dummy_con;
#endif

Then I select the console from the command line.

I can't vouch for the modified version in the kernel tree. My original
driver for the 69030 had a bug that made it fail if the VGA firmware had
already initialised the card. That wasn't a problem on the target
platform, but it is why I never submitted the driver to the kernel.


- Adrian Cox
Humboldt Solutions Ltd


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-06-22  7:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-20 20:40 Asiliantfb (Frame Buffer) Driver Dieu Morales
2004-06-21  8:24 ` Adrian Cox
2004-06-21 21:21   ` Dieu Morales
2004-06-22  7:05     ` Adrian Cox [this message]
2004-06-29  2:53       ` Dieu Morales
2004-06-21  8:47 ` Geert Uytterhoeven

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=1087887950.1547.98.camel@newt \
    --to=adrian@humboldt.co.uk \
    --cc=dieumorales@yahoo.com \
    --cc=linuxppc-dev@lists.linuxppc.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).