From: Pavel Machek <pavel@ucw.cz>
To: Dima Zavin <dima@android.com>
Cc: Brian Swetland <swetland@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Rebecca Schultz Zavin <rebecca@android.com>,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: Framebuffer support for HTC Dream
Date: Wed, 8 Jul 2009 11:19:31 +0200 [thread overview]
Message-ID: <20090708091930.GA24385@elf.ucw.cz> (raw)
In-Reply-To: <404ea8000906291606u600673f3r63a9ac0dfe02eea@mail.gmail.com>
Hi!
> >> > Will it have a maintainer?
> >>
> >> I did the original quick and dirty version for bringup. Rebecca took
> >> over and (re)wrote the bulk of the driver, getting things stable for
> >> production ship of Dream and Sapphire, and Dima is currently adding
> >> support for later Qualcomm chipsets (QSD8x50, etc). Looping them into
> >> this discussion.
> >
> > I can maintain it if noone else steps up. Of course, someone who
> > actually knows the hw/has the docs would be preferable.
>
> As Brian mentioned, I'm the last one to touch it here, so I now own
> it. I've done a bunch refactoring to add support for the qsd8x50
Can you submit a patch adding yourself into MAINTAINERS file?
> devices. I'll post those up onto our experimental git tree (hopefully
> sometime today), and once this patch goes in, I'll make sure that we
> apply cleanly against it. Alternatively, if you like, I can
> incorporate your comments into the refactoring work I'm doing, and can
> push out the combined patch. In the future though, I'll try to be a
> lot more aggressive at sending these out for review earlier so you
> don't have to clean up our mess.
I believe it makes sense to submit patches relative to -mm tree now.
> Please feel free to CC Rebecca and myself on all the msm_fb related
> changes/discussions.
>
> >> It would probably be worth referring to drivers like this as "for
> >> Qualcomm MSM/QSD SoCs" or the like, since they do work with a lot of
> >> hardware beyond just Dream.
> >
> > Well, the Dream is why I'm doing it, hence patch title. Of course,
> > Kconfig should say 'Qualcomm MSM/QSD SoCs', too.
>
> I second the request that the patches for qualcomm msm7k/qsd8k generic
> support would have descriptions that refer to them as such, since the
> htc dream specific code is only in the board files in
> arch/arm/mach-msm. Note that the HTC Magic (aka the Ion, myTouch 3G,
Ok, I guess someone should do a picture of all the connections and
dictionary of all the acronyms :-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-07-08 9:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 11:10 Framebuffer support for HTC Dream Pavel Machek
2009-06-29 19:38 ` Andrew Morton
2009-06-29 20:00 ` Brian Swetland
2009-06-29 21:19 ` Pavel Machek
2009-06-29 23:06 ` Dima Zavin
2009-07-08 9:19 ` Pavel Machek [this message]
2009-07-09 9:48 ` Pavel Machek
2009-06-29 19:41 ` Andrew Morton
2009-10-26 22:11 ` Jean-Christophe PLAGNIOL-VILLARD
2009-10-28 22:11 ` Add missing header for HTC Dream framebuffer Pavel Machek
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=20090708091930.GA24385@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=dima@android.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rebecca@android.com \
--cc=swetland@google.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).