linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Krzysztof Helt" <krzysztof.h1@wp.pl>
To: linux-fbdev-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH] tdfxfb: mtrr support (2nd revision)
Date: Fri, 03 Aug 2007 05:24:51 +0200	[thread overview]
Message-ID: <46b2a00372bf9@wp.pl> (raw)
In-Reply-To: LINKIFYCdaIJfFeaDeGbaeBHcJJFDIaGCEGfGJJEBIcDECdLINKIFYDfJAaHcHaFEBCadAcFJCdJGfBaEafaAeCHefJHFFLINKIFYAcDeCdDADccdBDHeIFbaJaeabdAHDAdGECeeIaGb <Pine.LNX.4.64.0708021952550.5150@anakin>

Dnia 2-08-2007 o godz. 19:56 Geert Uytterhoeven napisa³(a):
> On Tue, 31 Jul 2007, Krzysztof Helt wrote:
> >  
> > +	default_par->mtrr_handle = -1;
> > +	if (!nomtrr)
> > +		default_par->mtrr_handle =
> > +			mtrr_add(tdfx_fix.smem_start, tdfx_fix.smem_len,
> > +				 MTRR_TYPE_WRCOMB, 1);
> > +
> 
> ... but everything works nicely, because no callers of 
mttr_{add,del}()
> check for actual errors ;-)
> 
>

Actually, there is an indirect check. The mttr handle is freed 
only if mtrr_add returned no error value. That's why the mtrr_add 
"dummy" must return an error.

I agree, that I do not print any message that inform about 
failure of mtrr_add, but any other fb driver does not, either. I 
think the message does not make any sense (as the CPU may be not 
able to handle this - early x86 - or the mttr is disable in 
config - require more ifdefs for messages).

Regards,
Krzysztof

----------------------------------------------------
06.10.07. Sensation White, Hala Ludowa, Wroc³aw 
Wyst±pi±: Michael Burian, Angelo Mike & John Hetmond,
Sebastian Ingrosso, David Guetta, Markus Schulz, Sander Van Doorn.
Ostatnia pula biletów: http://klik.wp.pl/?adr=http%3A%2F%2Fadv.reklama.wp.pl%2Fas%2Fwhites.html&sid=1245



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

      reply	other threads:[~2007-08-03  3:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-29 21:06 [PATCH] tdfxfb: mtrr support Krzysztof Helt
2007-07-29 23:16 ` Antonino A. Daplas
2007-07-30 11:58   ` Krzysztof Helt
2007-07-31  9:55   ` [PATCH] tdfxfb: mtrr support (2nd revision) Krzysztof Helt
2007-08-02 17:56     ` Geert Uytterhoeven
2007-08-03  3:24       ` Krzysztof Helt [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=46b2a00372bf9@wp.pl \
    --to=krzysztof.h1@wp.pl \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).