All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Peres <martin.peres-BktLLJ5BOkI@public.gmane.org>
To: Ben Skeggs <skeggsb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Martin Peres
	<martin.peres-/ze9ptdxDJdQFI55V6+gNQ@public.gmane.org>,
	"nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [PATCH 1/2] drm/nouveau/bios/therm: handle vbioses with duplicate entries (mostly nva5)
Date: Mon, 09 Sep 2013 00:46:33 +0200	[thread overview]
Message-ID: <522CFE49.8050603@labri.fr> (raw)
In-Reply-To: <CACAvsv5VTQvVcQhB0_=GY4Jjx=3-EAd+QMqzemR7qsDeh7KxzA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 04/09/2013 03:55, Ben Skeggs wrote:
> On Sat, Aug 31, 2013 at 9:58 AM, Martin Peres <martin.peres-GANU6spQydw@public.gmane.org> wrote:
>> From: Martin Peres <martin.peres-BktLLJ5BOkI@public.gmane.org>
>>
>> Some vbioses have extra useless entries after "the end" of the table. This is
>> problematic since all of the vbios I found with this issue redefine the
>> pwm freq divider to insane levels (52750 Hz instead of 2500), thus breaking
>> fan management.
>>
>> The first solution to solve this mess would be to change the length of the
>> table. The solution I choose was simply to avoid setting the pwm freq twice
>> as the other redefinitions are harmless with our current parser.
> I'm still *really* not convinced we're using the thermal table correctly....
>
> However, this makes sense for our current handling, so, merged.
>
> Thanks,
> Ben.

Well, I do agree that the first versions of the vbios table really felt 
like a script but this isn't the case anymore (not sure how I tested 
this though as it was more than a year ago).

      parent reply	other threads:[~2013-09-08 22:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 23:58 [PATCH 1/2] drm/nouveau/bios/therm: handle vbioses with duplicate entries (mostly nva5) Martin Peres
     [not found] ` <1377907131-15099-1-git-send-email-martin.peres-GANU6spQydw@public.gmane.org>
2013-08-30 23:58   ` [PATCH 2/2] drm/nv84/therm: ack any pending IRQ at init Martin Peres
     [not found]     ` <1377907131-15099-2-git-send-email-martin.peres-GANU6spQydw@public.gmane.org>
2013-08-31  0:06       ` [PATCH] drm/nouveau/therm: ack any pending IRQ at init v2 Martin Peres
     [not found]         ` <1377907571-15301-1-git-send-email-martin.peres-GANU6spQydw@public.gmane.org>
2013-09-04  1:52           ` Ben Skeggs
     [not found]             ` <CACAvsv6+9TqeTjMeMPdAwDrxLbbZ1sBJDQFmE7Xum9ryebns7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-08 22:44               ` Martin Peres
2013-08-31  0:08   ` [PATCH 1/2] drm/nouveau/bios/therm: handle vbioses with duplicate entries (mostly nva5) Martin Peres
2013-09-04  1:55   ` Ben Skeggs
     [not found]     ` <CACAvsv5VTQvVcQhB0_=GY4Jjx=3-EAd+QMqzemR7qsDeh7KxzA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-08 22:46       ` Martin Peres [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=522CFE49.8050603@labri.fr \
    --to=martin.peres-bktllj5boki@public.gmane.org \
    --cc=martin.peres-/ze9ptdxDJdQFI55V6+gNQ@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=skeggsb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.