From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren 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 Message-ID: <20081208172642.GP7388@atomide.com> References: <1224545064-25551-1-git-send-email-mans@mansr.com> <20081206001153.GO9714@atomide.com> <20081206021256.GY9714@atomide.com> <1228748075.8668.90.camel@tubuntu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mho-01-bos.mailhop.org ([63.208.196.178]:52819 "EHLO mho-01-bos.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751251AbYLHR0p (ORCPT ); Mon, 8 Dec 2008 12:26:45 -0500 Content-Disposition: inline In-Reply-To: <1228748075.8668.90.camel@tubuntu> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Tomi Valkeinen Cc: linux-omap@vger.kernel.org * Tomi Valkeinen [081208 06:55]: > Hi, >=20 > On Fri, 2008-12-05 at 18:12 -0800, ext Tony Lindgren wrote: > > * M=E5ns Rullg=E5rd [081205 17:40]: > > > Tony Lindgren writes: > > >=20 > > > > M=E5ns, I heard you have some display patches? How about queuin= g up > > > > those on the fbdev list? > > >=20 > > > It looks like Tomi's driver is shaping up nicely, so it's probabl= y not > > > worthwhile spending any significant time on the current driver. = If > > > anyone is interested, everything I have is in my git tree. > >=20 > > OK, good to know. Tomi, do you have a git branch against the > > mainline kernel for your driver? > >=20 > > We could start mirroring it on linux-omap and then start automergin= g > > it on daily basis to linux-omap for testing (Assuming it does not c= ause > > problems with other stuff :) >=20 > I have a git tree against current linux-omap tree at > http://www.bat.org/~tomba/git/linux-omap-dss.git >=20 > It is possible to have a branch based on Linus' tree also, but it's m= ore > 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) waiti= ng > 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. >=20 > But after that I'm all for it.=20 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 i= t's > a good idea to break the old working code with new experimental code = =3D). > So I think I'll see if I can easily separate the old and new boot tim= e > memory allocation. Well we need to get rid of the old OMAP_TAGs too. > But what does it mean in practice?=20 >=20 > Mirroring means you (script?) will fetch a branch from my tree to dss= 2 > 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" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html