All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Costabel <costabel@wanadoo.fr>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org, debian-powerpc@lists.debian.org
Subject: Re: [PATCH] Minor changes to control/imstt/platinum/valkyrie/atyfb
Date: Sat, 01 Dec 2001 13:41:20 +0100	[thread overview]
Message-ID: <3C08CFF0.18A1FBC7@wanadoo.fr> (raw)
In-Reply-To: 20011127143058.R13091@cpe-24-221-152-185.az.sprintbbd.net


Tom Rini wrote:
>
> Hello all.  The following patches make slight changes to the vmode/cmode
> logic on a few fb drivers.  Now everone consistantly only tries to get
> these modes from nvram if CONFIG_NVRAM is defined (otherwise a
> compile-time error on everyone but atyfb).  On imsttfb I made the logic
> only executed on CONFIG_ALL_PPC, and removed USE_NV_MODES (which
> shouldn't be needed now).  However, I have none of this hardware, and I
> remember some of these drivers being very touchy.  So could people with
> this hardware apply the patch and let me know if it works still?

For the valkyriefb driver on my Pmac 6400, I can confirm from a first
short test that it still works. This is with your patch applied to
today's 2.4.17-pre1-ben0 kernel.

I am not testing it very extensively, because this kernel crashes on me
as soon as pppd is started. Yesterday's 2.4.16-ben0 crashed when running
ping. Even on my iBook, the 2.4.16 gave me an "illegal lseek" when
trying to run ping (the 2.4.17-pre1 seems to work OK on the iBook).
Since the 6400 is serving as an adsl router, I prefer to go back to the
stable 2.4.0-pmac kernel from last January.

--
Martin

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

  parent reply	other threads:[~2001-12-01 12:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-27 21:30 [PATCH] Minor changes to control/imstt/platinum/valkyrie/atyfb Tom Rini
2001-11-28  9:14 ` Geert Uytterhoeven
2001-12-28 11:28   ` Benjamin Herrenschmidt
2001-12-02 16:35     ` Tom Rini
2001-12-01 12:41 ` Martin Costabel [this message]
2001-12-02 10:14   ` Paul Mackerras
2001-12-02 21:11     ` Martin Costabel
2001-12-02 22:47       ` Paul Mackerras
2001-12-03 13:16       ` Geert Uytterhoeven
2001-12-03 15:09         ` Tom Rini
2001-12-05 11:22           ` Martin Costabel
  -- strict thread matches above, loose matches on Subject: below --
2001-12-03  8:10 Bill Fink
2001-12-02 23:59 ` Benjamin Herrenschmidt
2001-12-03 15:29   ` 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=3C08CFF0.18A1FBC7@wanadoo.fr \
    --to=costabel@wanadoo.fr \
    --cc=debian-powerpc@lists.debian.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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.