All of lore.kernel.org
 help / color / mirror / Atom feed
From: war <war@starband.net>
To: paulus@samba.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.16 Bug (PPC)
Date: Tue, 27 Nov 2001 17:02:14 -0500	[thread overview]
Message-ID: <3C040D66.BB8BAD19@starband.net> (raw)
In-Reply-To: <3C028378.50CA616C@starband.net> <15364.1721.506563.253393@gargle.gargle.HOWL>

Already learned how to fix this earlier, had to have nvram compiled in.


Paul Mackerras wrote:

> war writes:
>
> > 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.
>
> Gratuitous rudeness will usually get you an answer. :)
>
> > 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.
>
> Have you reported this before, on this list or anywhere else?
>
> The problem is that your config is slightly unusual in that you have
> turned off CONFIG_NVRAM.  We can put some ifdefs in so that it
> compiles without CONFIG_NVRAM.  For now, just turn on CONFIG_NVRAM.
>
> Paul.


      reply	other threads:[~2001-11-27 22:02 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
2001-11-27 21:33 ` Paul Mackerras
2001-11-27 22:02   ` war [this message]

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=3C040D66.BB8BAD19@starband.net \
    --to=war@starband.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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.