From: Anatolij Gustschin <agust@denx.de>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: Dmitry Baryshkov <dbaryshkov@gmail.com>,
Matteo Fortini <m.fortini@selcomgroup.com>,
linux-kernel@vger.kernel.org,
Krzysztof Helt <krzysztof.h1@poczta.fm>,
linuxppc-dev@ozlabs.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mb862xx: Restrict compliation of platform driver to PPC
Date: Fri, 23 Jan 2009 11:31:40 +0100 [thread overview]
Message-ID: <49799C8C.80903@denx.de> (raw)
In-Reply-To: <646765f40901191800y27530acaw74edc01abdd13e68@mail.gmail.com>
Julian Calaby wrote:
> On Tue, Jan 20, 2009 at 12:19, Anton Vorontsov <avorontsov@ru.mvista.com> wrote:
>> Should be Anatolij. ;-)
>
> Who is the first person on the list, I guess he's missed this or isn't
> reading his email.
I missed this, sorry.
> Before we commit to fixing this properly, is it really worth it? Is
> this hardware ever likely to be used with SPARC?
I don't think it will ever be used with SPARC, so your patch is Ok.
> Given that there are PCI and OF versions of the driver, it seems to me
> that this is available as a PCI expansion card, and as a graphics chip
> built into some PPC motherboards. The initial commit says: "Lime GDC
> support is known to work on PPC440EPx based lwmon5 and MPC8544E based
> socrates embedded boards, both equipped with Lime GDC." so I'm
> guessing that this graphics chip is designed for embedded boards. I
> can find references to it's use in embedded automotive applications on
> Google but I can't find any reference to the Fujitsu LIME (MB86276)
> and SPARC on Google.
If LIME chip should ever be used with SPARC, support for this
could be added later. LIME doesn't have PCI interface, it is
connected to the host cpu bus. PCI version of the driver is for
CoralP and Carmine chips which have PCI interface.
Anatolij
next prev parent reply other threads:[~2009-01-23 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 0:06 [PATCH] mb862xx: Restrict compliation of platform driver to PPC Julian Calaby
2009-01-20 0:50 ` Julian Calaby
2009-01-20 1:19 ` Anton Vorontsov
2009-01-20 2:00 ` Julian Calaby
2009-01-23 10:31 ` Anatolij Gustschin [this message]
2009-01-20 13:57 ` Anatolij Gustschin
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=49799C8C.80903@denx.de \
--to=agust@denx.de \
--cc=akpm@linux-foundation.org \
--cc=dbaryshkov@gmail.com \
--cc=julian.calaby@gmail.com \
--cc=krzysztof.h1@poczta.fm \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=m.fortini@selcomgroup.com \
/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).