From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Branch for fbdriver (Re: [PATCH 1/2] OMAP: Make dpll4_m4_ck programmable with clk_set_rate())
Date: Mon, 8 Dec 2008 09:26:44 -0800 [thread overview]
Message-ID: <20081208172642.GP7388@atomide.com> (raw)
In-Reply-To: <1228748075.8668.90.camel@tubuntu>
* Tomi Valkeinen <tomi.valkeinen@nokia.com> [081208 06:55]:
> Hi,
>
> On Fri, 2008-12-05 at 18:12 -0800, ext Tony Lindgren wrote:
> > * Måns Rullgård <mans@mansr.com> [081205 17:40]:
> > > Tony Lindgren <tony@atomide.com> writes:
> > >
> > > > Måns, I heard you have some display patches? How about queuing up
> > > > those on the fbdev list?
> > >
> > > It looks like Tomi's driver is shaping up nicely, so it's probably not
> > > worthwhile spending any significant time on the current driver. If
> > > anyone is interested, everything I have is in my git tree.
> >
> > OK, good to know. Tomi, do you have a git branch against the
> > mainline kernel for your driver?
> >
> > We could start mirroring it on linux-omap and then start automerging
> > it on daily basis to linux-omap for testing (Assuming it does not cause
> > problems with other stuff :)
>
> I have a git tree against current linux-omap tree at
> http://www.bat.org/~tomba/git/linux-omap-dss.git
>
> It is possible to have a branch based on Linus' tree also, but it's more
> maintenance work as I need a bunch of omap patches that are not in
> Linus' tree. (Actually, I have never tested DSS2 with Linus' tree, so
> I'm not sure how much stuff there's missing).
Well let's see what needs to be patched outside drivers/video and get
it merged to mainline so you can maintain your patches against the
mainline tree.
If something is not in the mainline for drivers/video, we can try to
get those integrated to mainline, or add them to your queue for now.
> I'd like to get the DSS2 working on OMAP2 also, but I'm (still) waiting
> for my N810. Half a year ago the DSS2 did work on OMAP2, but I'm sure
> it's since been broken, and needs some healing.
>
> But after that I'm all for it.
OK
> However, there is a small breakage because of the VRAM manager and
> OMAP_TAG removal. That code is common for the old and new DSS. I have a
> patch to fix the old DSS to use the VRAM manager, but I don't think it's
> a good idea to break the old working code with new experimental code =).
> So I think I'll see if I can easily separate the old and new boot time
> memory allocation.
Well we need to get rid of the old OMAP_TAGs too.
> But what does it mean in practice?
>
> Mirroring means you (script?) will fetch a branch from my tree to dss2
> branch on linux-omap tree?
Yes, I'll git-fetch your branch automatically once a day.
> What does automerging mean?
I'll merge your branch into linux-omap master branch once a day
automatically.
> Does it mean I can still continue rebasing my tree to keep it clean?
Yes!
Tony
--
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-12-08 17:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 12:11 Setting dss1_alwon_fck Tomi Valkeinen
2008-10-20 23:23 ` Måns Rullgård
2008-10-20 23:24 ` [PATCH 1/2] OMAP: Make dpll4_m4_ck programmable with clk_set_rate() Mans Rullgard
2008-12-05 23:52 ` Paul Walmsley
2008-12-06 0:11 ` Tony Lindgren
2008-12-06 1:03 ` Paul Walmsley
2008-12-06 1:10 ` Tony Lindgren
2008-12-06 1:40 ` Måns Rullgård
2008-12-06 2:12 ` Branch for fbdriver (Re: [PATCH 1/2] OMAP: Make dpll4_m4_ck programmable with clk_set_rate()) Tony Lindgren
2008-12-08 14:54 ` Tomi Valkeinen
2008-12-08 17:26 ` Tony Lindgren [this message]
2008-10-20 23:24 ` [PATCH 2/2] OMAP: Add clk_get_parent() for OMAP2/3 Mans Rullgard
2008-12-05 23:52 ` Paul Walmsley
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=20081208172642.GP7388@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@nokia.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