[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a55d774e0906291300u3bb9b491r124f27fdf832b495@mail.gmail.com>
Date: Mon, 29 Jun 2009 13:00:33 -0700
From: Brian Swetland <swetland@...gle.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
Rebecca Schultz Zavin <rebecca@...roid.com>,
Dima Zavin <dima@...roid.com>
Cc: Pavel Machek <pavel@....cz>,
linux-fbdev-devel@...ts.sourceforge.net,
linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.arm.linux.org.uk
Subject: Re: Framebuffer support for HTC Dream
On Mon, Jun 29, 2009 at 12:38 PM, Andrew
Morton<akpm@...ux-foundation.org> wrote:
> On Mon, 29 Jun 2009 13:10:30 +0200
> Pavel Machek <pavel@....cz> wrote:
>> I cleaned up dead code, a lot of debugging infastructure and horrific
>> logo code. I had to remove earlysuspend support, because neccessary
>> headers are not in mainline. The driver still works :-).
>
> So you didn't wrote the code?
>
>> This adds support for framebuffer on HTC Dream smartphone (aka
>> T-Mobile G1, aka ADP1).
>>
>> Signed-off-by: Pavel Machek <pavel@....cz>
>> Cc: Brian Swetland <swetland@...gle.com>
>
> Someone did. Are the signoffs and attributions correct and
> appropriate? Should we at least mention the driver's history in the
> changelog?
>
> 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.
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.
Brian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists