All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam C Powell IV <hazelsct@mit.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Why require CONFIG_BOOTX_TEXT for so much of offb?
Date: Mon, 10 Dec 2001 23:11:04 -0500	[thread overview]
Message-ID: <3C158758.5020608@mit.edu> (raw)


Greetings,

Somewhere between 2.4.8 and 2.4.12, the benh kernel (used by Dan
Jacobowitz in Debian) wrapped much of offb_init() in
#ifdef CONFIG_BOOTX_TEXT

As a result of this, the Debian kernel images, which do not set
CONFIG_BOOTX_TEXT because of oldworld OF problems, cannot open video
using BootX (unless you specify e.g. video=atyfb...).

So here are my questions:

    * Is there a way around this?
    * Is the test for BootX at the start of offb_init() somehow
      insufficient, such that all of this code must be eliminated if
      non-BootX booting is to work?
    * Or is there in fact a hard dependency of that code on other stuff
      provided by CONFIG_BOOTX_TEXT?
    * Is there some way of separating the two, so a single kernel can
      work with BootX and with all versions of OpenFirmware?
    * What's the point of offb without this section of code?

Please CC me in replies, as I'm not subscribed to this list.

Thanks,
--

-Adam P.

GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

Welcome to the best software in the world today cafe!
<http://lyre.mit.edu/%7Epowell/The_Best_Stuff_In_The_World_Today_Cafe.ogg>


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

             reply	other threads:[~2001-12-11  4:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-11  4:11 Adam C Powell IV [this message]
2001-12-12 19:05 ` Why require CONFIG_BOOTX_TEXT for so much of offb? Peter Bergner
2001-12-13  2:00   ` Tom Rini
2001-12-13 16:58     ` Peter Bergner
2001-12-13 17:04       ` Tom Rini

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=3C158758.5020608@mit.edu \
    --to=hazelsct@mit.edu \
    --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 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.