linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	linux-fbdev-devel@lists.sourceforge.net,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nvidiafb: PPC & mode setting fixes (#2)
Date: Sun, 02 Oct 2005 18:02:06 +1000	[thread overview]
Message-ID: <1128240126.8267.37.camel@gaston> (raw)
In-Reply-To: <433F8774.6000301@gmail.com>

On Sun, 2005-10-02 at 15:08 +0800, Antonino A. Daplas wrote:
> Benjamin Herrenschmidt wrote:
> > (This version removes a useless bit that slipped in the previous one)
> > 
> > This patch fixes a couple of things in nvidiafb:
> > 
> >  - The code for retreiving the mode from Open Firmware was broken. It
> > would crash at boot and was copied from the old rivafb code that didn't
> > work very well (I'll update rivafb too one of these days).
> 
> What do you think of making EDID retrieval from the OF generic?  Or is
> it too much hassle?

Well, at this point, it only really concerns nvidia and ati's and their
respective firmwares seem to expose some properties a bit differently...
The radeon code would probably work for nvidia though as I'm not trying
to get the connector type for nvidiafb yet, but if I ever try, it seems
the stuff is a bit different.

I'd say let's keep them separate for now, I may put them in a common
place some day ..

Ben.

> Thanks for the fix :-)  
> 
> Acked-by: Antonino Daplas <adaplas@pol.net>

Ok, if you confirm it doesn't seem to do any regression on other
hardware (I don't have any other nvidia hw to test with), I'd like it
upstream asap (probably too late for 2.6.14 though).

Ben.

      reply	other threads:[~2005-10-02  8:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-02  3:57 [PATCH] nvidiafb: PPC & mode setting fixes Benjamin Herrenschmidt
2005-10-02  5:49 ` [PATCH] nvidiafb: PPC & mode setting fixes (#2) Benjamin Herrenschmidt
2005-10-02  7:08   ` Antonino A. Daplas
2005-10-02  8:02     ` Benjamin Herrenschmidt [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=1128240126.8267.37.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=adaplas@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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).