From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Thibaut VARENE <varenet@esiee.fr>
Cc: Thibaut VARENE <T-Bone@parisc-linux.org>,
linux-fbdev-devel@lists.sourceforge.net,
Antonino Daplas <adaplas@pol.net>,
Ben Dooks <ben-linux-arm@fluff.org>
Subject: Re: [PATCH][RFC] Add support for Epson S1D13806 FB
Date: Mon, 14 Mar 2005 21:13:57 +0800 [thread overview]
Message-ID: <200503142113.57518.adaplas@hotpop.com> (raw)
In-Reply-To: <20050314130014.55A073658E8@mail.esiee.fr>
On Monday 14 March 2005 21:00, Thibaut VARENE wrote:
> > 3. You can use pci_resource_len()/pci_resource_start() instead of
>
> Actually I don't think so: this chip is often found on embedded
> platforms that don't have PCI bus. Hence all the
> platform_device/platform_data glue in the driver. My understanding is
> that pci_resource_* macros are only available when CONFIG_PCI is
> enabled. As far as I can tell from the documentation, there's no PCI
> version of that chip family. That's also the reason why the Kconfig
> option only depends on CONFIG_FB.
Ok then.
>
> > No need, I'll take care of merging the driver.
>
> Thanks! Please let me know if the attached patch is suitable for
> inclusion into mainline :)
>
Should be okay. I'll push it to the mm tree first, and eventually, to
mainline.
Tony
-------------------------------------------------------
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_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-14 13:14 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 [this message]
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
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=200503142113.57518.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=T-Bone@parisc-linux.org \
--cc=adaplas@pol.net \
--cc=ben-linux-arm@fluff.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=varenet@esiee.fr \
/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.