All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miles Lane <miles.lane@gmail.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-fbdev-devel@lists.sourceforge.net,
	Andrew Morton <akpm@osdl.org>,
	khali@linux-fr.org
Subject: Re: Re: 2.6.12-rc1-mm2 -- nvidiafb driver gives black screen
Date: Mon, 28 Mar 2005 16:56:38 -0800	[thread overview]
Message-ID: <a44ae5cd0503281656592e6177@mail.gmail.com> (raw)
In-Reply-To: <42483B11.6010203@osdl.org>

On Mon, 28 Mar 2005 09:12:49 -0800, Randy.Dunlap <rddunlap@osdl.org> wrote:

By the why, I don't know why Andrew got dropped from my previous message list.
Also, I thought you were asking these questions of the fbdev and
vidiafb developers.

> I guess that there is some chance that the io_remap_pfn* patches
> are involved with this.  

I am a tester, so I don't have knowledge about this.

> Is there some way to determine exactly which
> io remap kernel calls are involved in "nvidiafb: cannot ioremap FB
> base" ?  

I don't know.  Someone who does, please tell me.  If someone
will tell me how, I'll be happy to gather the information.

> Is that in the exposed source code?  

I have no idea.  How would I find out?

> If so, where is that source code?  

I have no clue.

> If not, can we determine from the binary which calls
> are being made?  

Uhhh.  I have delivered the Oops info and a bunch of other
information.  I have given you whatever I thought might be helpful.  I
need guidance here.

> Or should I just make a io_remap debug patch that
> prints out lots of debug info so that we can track this down?

I thought you would determine this with input from developers.

Your humble tester (remember me from the early USB days?),

      Miles


-------------------------------------------------------
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  0:56 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 [this message]
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
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=a44ae5cd0503281656592e6177@mail.gmail.com \
    --to=miles.lane@gmail.com \
    --cc=akpm@osdl.org \
    --cc=khali@linux-fr.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --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 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.