public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Gerst <bgerst@didntduck.org>
To: war <war@starband.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.16 Bug (PPC)
Date: Mon, 26 Nov 2001 13:35:15 -0500	[thread overview]
Message-ID: <3C028B63.3A6AF1EC@didntduck.org> (raw)
In-Reply-To: <3C028378.50CA616C@starband.net>

war wrote:
> 
> Bug still resides in 2.4.16 still, even after the PPC fixes that were
> applied to 2.4.16-pre1.
> 
> If nobody cares about PPC updates, I guess I should put the box back on
> the shelf.
> 
> The video driver (plat) is the framebuffer for a few macs, without it,
> I cannot do anything.
> 
> Any plans to fix this?
> 
> //              default_vmode = nvram_read_byte(NV_VMODE);
> //              default_cmode = nvram_read_byte(NV_CMODE);
> 
> Commenting the two undefined functions out in drivers/video/platinumfb.c
> allows for a successful compile.
> It also allows for the video driver to be brought up succesfully.
> 
> Now will this bug be fixed in 2.4.17 for PPC or should I just put my PPC
> back on the shelf? :)

Is CONFIG_NVRAM built in to the kernel?

--

				Brian Gerst

  parent reply	other threads:[~2001-11-26 18:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-26 18:01 Linux 2.4.16 Bug (PPC) war
2001-11-26 18:07 ` Rik van Riel
2001-11-26 18:14 ` Russell King
2001-11-26 17:07   ` Marcelo Tosatti
2001-11-26 18:37   ` Tom Rini
2001-11-27 21:29   ` Paul Mackerras
2001-11-26 18:34 ` Tom Rini
2001-11-26 18:35 ` Brian Gerst [this message]
2001-11-27 21:33 ` Paul Mackerras
2001-11-27 22:02   ` war

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=3C028B63.3A6AF1EC@didntduck.org \
    --to=bgerst@didntduck.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=war@starband.net \
    /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