linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thibaut VARENE <varenet@esiee.fr>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Frame Buffer Device Development
	<linux-fbdev-devel@lists.sourceforge.net>,
	Thibaut VARENE <T-Bone@parisc-linux.org>,
	Antonino Daplas <adaplas@pol.net>,
	Ben Dooks <ben-linux-arm@fluff.org>
Subject: Re: Re: [PATCH][RFC] Add support for Epson S1D13806 FB
Date: Mon, 14 Mar 2005 14:34:27 +0100	[thread overview]
Message-ID: <20050314133427.56F31365905@mail.esiee.fr> (raw)
In-Reply-To: <Pine.LNX.4.62.0503141425000.4784@numbat.sonytel.be>

-------------------
> On Mon, 14 Mar 2005, Paul Mundt wrote:
> > On Mon, Mar 14, 2005 at 08:15:13PM +0800, Antonino A. Daplas
wrote:
> > > 3. You can use pci_resource_len()/pci_resource_start() instead
of
> > > 
> > > +	info->fix.mmio_start = pdev->resource[1].start;
> > > +	info->fix.mmio_len = pdev->resource[1].end -
pdev->resource[1].start;
> 
> +1?
> 
> > > +	info->fix.smem_start = pdev->resource[0].start;
> > > +	info->fix.smem_len = pdev->resource[0].end -
pdev->resource[0].start;
> 
> +1?
> 
> > > +
> > > 
> > No, the pdev here refers to a platform device, not a pci device.
> > 
> > While the pci_resource_xxx() routines would still technically do
the
> > right thing, this is purely coincidental.
> 
> Nah, they would work better here, since they do include the +1 ;-)

Good point. Actually that's a bad thing we did on our platform: we
didn't add the '-1' to the platform device ranges, so there was no
need for the '+1'.

I guess it's The Good Thing to do to add a '+1' here, I'll take care
of changing our platform specific bits to match this.

Thanks for pointing that out.

Let me know if I should resubmit the patch.

Thibaut VARENE


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click

  reply	other threads:[~2005-03-14 13:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 10:13 [PATCH][RFC] Add support for Epson S1D13806 FB Thibaut VARENE
2005-03-14 12:15 ` Antonino A. Daplas
2005-03-14 13:00   ` Thibaut VARENE
2005-03-14 13:13     ` Antonino A. Daplas
2005-03-14 14:10     ` Antonino A. Daplas
2005-03-14 14:24       ` Thibaut VARENE
2005-03-14 15:06         ` Antonino A. Daplas
2005-03-14 14:35       ` Paul Mundt
2005-03-14 15:06         ` Antonino A. Daplas
2005-03-15  7:17           ` Paul Mundt
2005-03-15 10:26             ` Antonino A. Daplas
2005-03-14 15:18         ` Antonino A. Daplas
2005-03-14 13:18   ` Paul Mundt
2005-03-14 13:25     ` Geert Uytterhoeven
2005-03-14 13:34       ` Thibaut VARENE [this message]
2005-03-14 13:53         ` Antonino A. Daplas
2005-03-14 14:09           ` Thibaut VARENE
2005-03-14 14:12           ` Thibaut VARENE
2005-03-14 13:44       ` Paul Mundt

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=20050314133427.56F31365905@mail.esiee.fr \
    --to=varenet@esiee.fr \
    --cc=T-Bone@parisc-linux.org \
    --cc=adaplas@pol.net \
    --cc=ben-linux-arm@fluff.org \
    --cc=geert@linux-m68k.org \
    --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).