From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: "ext Måns Rullgård" <mans@mansr.com>
Cc: linux-omap@vger.kernel.org, video4linux-list@redhat.com
Subject: Re: [PREVIEW] New display subsystem for OMAP2/3
Date: Wed, 17 Sep 2008 10:32:42 +0300 [thread overview]
Message-ID: <1221636762.6312.117.camel@tubuntu> (raw)
In-Reply-To: <yw1xljxtxl8t.fsf@thrashbarg.mansr.com>
On Mon, 2008-09-15 at 20:27 +0100, ext Måns Rullgård wrote:
> Tomi Valkeinen <tomi.valkeinen@nokia.com> writes:
>
> > On Sat, 2008-09-13 at 22:47 +0100, ext Måns Rullgård wrote:
> >> Koen Kooi <k.kooi@student.utwente.nl> writes:
> >
> >> What I don't like about the patch posted is its size. I'm sure the
> >> transition could be done in a sequence of smaller patches. At the
> >> very least, it should be possible to move existing functionality to
> >> the new architecture, then add the new parts afterwards. I also see
> >> little value in keeping the old model around, as is done in the patch.
> >
> > I don't like the size either. However, I have no idea how the old driver
> > could be transformed to include this functionality with a reasonable
> > effort. The implementations are quite different.
> >
> > Any suggestions how I could approach this task? Only thing that comes to
> > my mind is that there are very similar low level functions in both DSS1
> > and DSS2 (for dispc and rfbi), that I could remove from the old place
> > and move to arch/arm/plat-omap/dss/, but that doesn't take us very far.
>
> Are the patches you posted your latest version of the code? Do you
> have this code in a public git repo? I'd like to take a closer look
> at what you've done.
They are not the very latest, but they are recent enough. Unfortunately
I don't have them on a public git. Nokia is still a bit lacking in that
area =). They should apply to linux-omap kernel from last Thursday (I
think the commit id is mentioned in the series file).
Tomi
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-09-17 7:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 14:55 [PREVIEW] New display subsystem for OMAP2/3 Tomi Valkeinen
2008-09-12 14:29 ` Shah, Hardik
2008-09-12 15:29 ` Daniel Stone
2008-09-13 20:27 ` Koen Kooi
2008-09-13 21:47 ` Måns Rullgård
2008-09-15 8:40 ` Shah, Hardik
2008-09-15 12:05 ` Tomi Valkeinen
2008-09-15 19:27 ` Måns Rullgård
2008-09-17 7:32 ` Tomi Valkeinen [this message]
2008-09-17 8:47 ` Måns Rullgård
2008-09-15 11:07 ` Tomi Valkeinen
2008-09-15 11:52 ` Shah, Hardik
2008-09-15 12:36 ` Tomi Valkeinen
2008-09-15 12:04 ` Daniel Stone
2008-09-15 13:32 ` Hiremath, Vaibhav
2008-09-15 14:38 ` Tomi Valkeinen
2008-09-15 16:20 ` Hiremath, Vaibhav
-- strict thread matches above, loose matches on Subject: below --
2008-10-01 10:51 Hiremath, Vaibhav
2008-10-02 8:24 ` Tomi Valkeinen
2008-10-03 12:47 ` Hiremath, Vaibhav
2008-10-03 13:25 ` Tomi Valkeinen
2008-10-03 13:34 ` Tony Lindgren
2008-10-03 14:16 ` Hiremath, Vaibhav
2008-10-24 9:50 ` Shah, Hardik
2008-10-03 14:03 ` Hans Verkuil
2008-10-03 14:19 ` Tomi Valkeinen
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=1221636762.6312.117.camel@tubuntu \
--to=tomi.valkeinen@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=mans@mansr.com \
--cc=video4linux-list@redhat.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