mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zeno Davatz <zdavatz@gmail.com>
To: "Éric Piel" <E.A.B.Piel@tudelft.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.34-rc3 - nvidia: module license 'NVIDIA' taints kernel.
Date: Wed, 31 Mar 2010 11:37:07 +0200	[thread overview]
Message-ID: <s2z40a4ed591003310237l6b4e85d4l99c97ae9602ea614@mail.gmail.com> (raw)
In-Reply-To: <4BB3166C.70408@tudelft.nl>

On Wed, Mar 31, 2010 at 11:31 AM, Éric Piel <E.A.B.Piel@tudelft.nl> wrote:
> 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...

Thank you for the quick response! Shall I contact any person that I
find at Nvidia or do you have a specific person that you recommend?

If you do not reply I will, just try to find a person at Nvidia.

Best
Zeno

      reply	other threads:[~2010-03-31  9:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31  9:18 Zeno Davatz
2010-03-31  9:31 ` Éric Piel
2010-03-31  9:37   ` Zeno Davatz [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=s2z40a4ed591003310237l6b4e85d4l99c97ae9602ea614@mail.gmail.com \
    --to=zdavatz@gmail.com \
    --cc=E.A.B.Piel@tudelft.nl \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®