linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Chris Boot <bootc@worldnet.fr>
To: LinuxPPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Changes in the Valkyrie driver from 2.1.24 to 2.2.18
Date: Wed, 03 Jan 2001 23:25:48 +0100	[thread overview]
Message-ID: <B6796554.7E88%bootc@worldnet.fr> (raw)


Hi,

It has struck me, after weeks of research, that my problems in booting my
5400/180 cold through OpenFirmware are caused by changes in the Linux
kernel.  This machine uses the Valkyrie display device, and in 2.1.24 this
is handled by directly accessing its memory, whereas in 2.2.18 it is
accessed through OpenFirmware.  OpenFirmware is known to choke on this
machine when using the display (as in CLAIM failed).

My suspicions were aroused when, after disabling CONFIG_FB, the machine
booted cold without any problems whatsoever.

Is it at all possible to use Valkyrie without going through OpenFirmware at
all?  It is not selectable if I disable CONFIG_FB_OF.  Would it be possible
to port the older non-OF driver to the newer kernel?  What are the
disadvantages of using the older memory-based driver to the newer OF-based
driver?

Thanks.

--
    .-.        Chris Boot
    /v\     bootc@worldnet.fr
   // \\
  /(   )\   L   I   N   U   X
   ^^-^^   >Phear the Penguin<


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

             reply	other threads:[~2001-01-03 22:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-03 22:25 Chris Boot [this message]
2001-01-03 22:51 ` Changes in the Valkyrie driver from 2.1.24 to 2.2.18 Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2001-01-04  6:43 Martin Costabel
2001-01-04 10:26 ` Chris Boot

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=B6796554.7E88%bootc@worldnet.fr \
    --to=bootc@worldnet.fr \
    --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).