From: "Éric Piel" <E.A.B.Piel@tudelft.nl>
To: Zeno Davatz <zdavatz@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.34-rc3 - nvidia: module license 'NVIDIA' taints kernel.
Date: Wed, 31 Mar 2010 11:31:24 +0200 [thread overview]
Message-ID: <4BB3166C.70408@tudelft.nl> (raw)
In-Reply-To: <y2r40a4ed591003310218he411c263p62915a3e0a5a8de3@mail.gmail.com>
On 31/03/10 11:18, Zeno Davatz wrote:
> Ok, I just booted into the new 2.6.34-rc3 Kernel. Looks Lovely!
:
> resource map sanity check conflict: 0x9f800 0xa07ff 0xa0000 0xbffff
:
> Info: mapping multiple BARs. Your kernel is fine.
:
>
> Can I ignore this or is this of any use for the list and the Kernel improvement?
Hi,
This is not tainting, it's a resource conflict. That check has just been
added to the kernel, that's why it did not happen before. As mentioned
in the log, your kernel is fine.
As the conflict is happening with the proprietary driver, the only
action you can do is to contact NVidia. Maybe they'll fix it in a later
version...
See you,
Eric
next prev parent reply other threads:[~2010-03-31 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 9:18 2.6.34-rc3 - nvidia: module license 'NVIDIA' taints kernel Zeno Davatz
2010-03-31 9:31 ` Éric Piel [this message]
2010-03-31 9:37 ` Zeno Davatz
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=4BB3166C.70408@tudelft.nl \
--to=e.a.b.piel@tudelft.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=zdavatz@gmail.com \
/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.