linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jean Delvare" <khali@linux-fr.org>
To: miles.lane@gmail.com, rddunlap@osdl.org
Cc: linux-fbdev-devel@lists.sourceforge.net, adaplas@pol.net
Subject: Re: Re: 2.6.12-rc1-mm2 -- nvidiafb driver gives black screen
Date: Tue, 29 Mar 2005 11:16:58 +0200 (CEST)	[thread overview]
Message-ID: <dJBFtcnM.1112087818.6686590.khali@localhost> (raw)
In-Reply-To: <a44ae5cd05032817125e99b868@mail.gmail.com>


Hi gentle folks,

> Perhaps you are thinking I am using the NVidia binary driver?
> This is not the case.  nvidiafb is a recently added framebuffer
> driver (IIRC, first showing up in 2.6.12-rc1-mm2).  I believe
> khali@linux-fr.org is the author.

I am not! Antonino Daplas is. Adding him to the CC list, although I guess
he reads linux-fbdev-devel.

The only part I can help with is the i2c stuff, which caused trouble
already, but so far I couldn't find anything relevant. The nvidiafb
driver is quite new, and it's natural that it needs some debugging. I
suspect that the driver has some severe problem with the way it handles
resources, as was suggested by our previous (failed) attempts to debug
it. I'd be happy to help with the debugging but unfortunately (no quite
so) I don't have any nvidia device in my machines anymore.

Somewhere else in this thread, Randy suggested that some __devinit stuff
wasn't really. I think it would be worth investigating this first, and
make sure that nothing is incorrectly tagged. The oops reported by Miles
sounded like large memory chunks had been freed when they shouldn't
have. I think I understand that erroneously tagging things __init might
lead to that kind of trouble. But maybe it's a completely different
problem, I'm really only suggesting this because I don't get what's
going on either.

Thanks,
--
Jean Delvare


-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/info/Sentarus/hamr30

  parent reply	other threads:[~2005-03-29  9:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a44ae5cd0503242023233dc23f@mail.gmail.com>
2005-03-25  4:31 ` 2.6.12-rc1-mm2 -- nvidiafb driver gives black screen Andrew Morton
2005-03-26  4:50   ` Miles Lane
2005-03-28 17:12     ` Randy.Dunlap
2005-03-29  0:22       ` Miles Lane
2005-03-29  0:37         ` Randy.Dunlap
2005-03-29  0:56       ` Miles Lane
2005-03-29  1:02         ` Randy.Dunlap
2005-03-29  1:12           ` Miles Lane
2005-03-29  3:01             ` Randy.Dunlap
2005-03-29  9:16             ` Jean Delvare [this message]
2005-03-29  1:13           ` Andrew Morton
2005-03-29  3:56             ` Miles Lane
2005-03-29  4:34     ` Randy.Dunlap
2005-03-29 16:25       ` [PATCH] nvidiafb: fix section references Randy.Dunlap
2005-04-14  5:51   ` Re: 2.6.12-rc1-mm2 -- nvidiafb driver gives black screen Antonino A. Daplas
2005-04-14 17:06     ` Jean Delvare
2005-04-15  3:07       ` Antonino A. Daplas
2005-04-14  5:51   ` Antonino A. Daplas
2005-04-14 17:13     ` Jean Delvare
2005-04-14 18:19       ` Miles Lane
2005-04-15  3:07         ` Antonino A. Daplas
2005-04-15  3:07       ` Antonino A. Daplas
2005-04-16  8:21         ` Miles Lane
2005-04-21  5:51           ` Miles Lane
2005-04-21 16:22             ` Randy.Dunlap
2005-04-21 18:36               ` Randy.Dunlap
2005-04-23  0:03                 ` Miles Lane
2005-04-23  0:12                   ` Miles Lane
2005-04-24 17:09                     ` Miles Lane
2005-04-25  3:21                       ` Antonino A. Daplas
2005-04-25 20:31                         ` Miles Lane
2005-04-25 20:33                         ` Miles Lane

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=dJBFtcnM.1112087818.6686590.khali@localhost \
    --to=khali@linux-fr.org \
    --cc=adaplas@pol.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=miles.lane@gmail.com \
    --cc=rddunlap@osdl.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).