linux-kernel - RE: [PATCH 00/18] OMAP: DSS2: Intro

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <19F8576C6E063C45BE387C64729E73940436BA4F6D@dbde02.ent.ti.com>
Date:	Fri, 11 Sep 2009 00:14:55 +0530
From:	"Hiremath, Vaibhav" <hvaibhav@...com>
To:	"tomi.valkeinen@...ia.com" <tomi.valkeinen@...ia.com>,
	ext Andrew Morton <akpm@...ux-foundation.org>
CC:	Artem Bityutskiy <dedekind1@...il.com>,
	"tony@...mide.com" <tony@...mide.com>,
	"Syed Mohammed, Khasim" <khasim@...com>,
	"sakoman@...il.com" <sakoman@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>
Subject: RE: [PATCH 00/18] OMAP: DSS2: Intro


> -----Original Message-----
> From: Tomi Valkeinen [mailto:tomi.valkeinen@...ia.com]
> Sent: Thursday, September 03, 2009 4:30 PM
> To: ext Andrew Morton
> Cc: Artem Bityutskiy; tony@...mide.com; Hiremath, Vaibhav; Syed
> Mohammed, Khasim; sakoman@...il.com; linux-kernel@...r.kernel.org;
> linux-omap@...r.kernel.org
> Subject: Re: [PATCH 00/18] OMAP: DSS2: Intro
> 
> Hi,
> 
> On Thu, 2009-09-03 at 00:11 +0200, ext Andrew Morton wrote:
> > On Tue, 01 Sep 2009 10:10:19 +0300
> > Artem Bityutskiy <dedekind1@...il.com> wrote:
> >
> > > Andrew,
> > >
> > > could you please help with merging this piece of (well written)
> code?
> > > Could you give your blessing to include it into linux-next now,
> and
> > > merge this during the next merge window?
> >
> > I'll merge them (after I've looked through them, which I'll do
> now).
> >
> > But there are more rejects than I'm prepared to cope with.  The
> various
> > arch/arm files have undergone some changes in linux-next which
> yield
> > more breakage than I'm prepared to try to fix.  For example,
> > arch/arm/mach-omap2/board-3430sdp.c:sdp3430_config[] ends up being
> an
> > empty array!
> 
> I rebased the patches on top of linux-next. The tree is at
> http://gitorious.org/linux-omap-dss2/linux , in branch linux-next-
> dss.
> 
> The only conflict was in board-3430sdp, and yes, sdp3430_config is
> supposed to end up as an empty array.
> 
[Hiremath, Vaibhav] I have refreshed OMAp3EVM patch support on top of l-o master, as of now I have shared it under 

http://arago-project.org/git/people/?p=vaibhav/ti-psp-omap-video.git;a=summary

under ti_display branch, and will be posting to L-O once DSS2 gets accepted.

> > Then there's the matter of these patches, already in -mm:
> >
> > omapfb-add-support-for-the-apollon-lcd.patch
> > omapfb-add-support-for-mipi-dcs-compatible-lcds.patch
> > omapfb-add-support-for-the-amstrad-delta-lcd.patch
> > omapfb-add-support-for-the-2430sdp-lcd.patch
> > omapfb-add-support-for-the-omap2evm-lcd.patch
> > omapfb-add-support-for-the-3430sdp-lcd.patch
> > omapfb-add-support-for-the-omap3-evm-lcd.patch
> > omapfb-add-support-for-the-omap3-beagle-dvi-output.patch
> > omapfb-add-support-for-the-gumstix-overo-lcd.patch
> > omapfb-add-support-for-the-zoom-mdk-lcd.patch
> > omapfb-add-support-for-rotation-on-the-blizzard-lcd-ctrl.patch
> > n770-enable-lcd-mipi-dcs-in-kconfig.patch
> > omapfb-dispc-various-typo-fixes.patch
> > omapfb-dispc-disable-iface-clocks-along-with-func-clocks.patch
> > omapfb-dispc-enable-wake-up-capability.patch
> > omapfb-dispc-allow-multiple-external-irq-handlers.patch
> > omapfb-suspend-resume-only-if-fb-device-is-already-
> initialized.patch
> > omapfb-fix-coding-style-remove-dead-line.patch
> > omapfb-add-fb-manual-update-option-to-kconfig.patch
> > omapfb-hwa742-fix-pointer-to-be-const.patch
> 
> These are not in linux-next, I think. They are for the old OMAP
> display
> subsystem, and may cause some conflicts with DSS2. I think those
> patches
> should go in also, as the old driver is used for OMAP1 and fo all
> the
> other boards that have not been ported to use DSS2.
> 
> Should I rebase DSS2 on top of -mm and solve the conflicts? If so,
> where
> can I find your tree?
> 
[Hiremath, Vaibhav] Andrew,
We have not heard anything back on this, when are you planning to merge DSS2?

Actually other development patches are gating because of this, like V4L2 driver on top of DSS2.

Thanks,
Vaibhav

>  Tomi
> 
> 

--
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/