All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Nicolas Dechesne <ndec13@gmail.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH v2 1/6] linux-omap4: update to ti-ubuntu-3.4-1487.6
Date: Fri, 12 Oct 2012 17:27:30 -0400	[thread overview]
Message-ID: <20121012212730.GE32601@denix.org> (raw)
In-Reply-To: <CAOT3miKQiE18HUPtFZBGctYdB4Kb2A_WOjStdy+RegPmOtM3Jw@mail.gmail.com>

On Fri, Oct 12, 2012 at 11:11:50PM +0200, Nicolas Dechesne wrote:
> On Fri, Oct 12, 2012 at 10:53 PM, Denys Dmytriyenko <denys@ti.com> wrote:
> >
> > https://github.com/rvfh/meta-ti/commit/6342c03a0dba7d906db09630e57e2372998428df
> >
> > The recipe itself is quite trivial (I even had my own version in the works)
> > and I only have couple minor fixes around SRCREV and its comment... But have
> > you compared the defconfigs between those two patches? I know the first
> > version of your patch used completely different unofficial defconfig... And
> > you didn't specify which one you have in v2. I'd prefer to use the defconfig
> > that was validated by the GLP team. Thanks.
> 
> i would still prefer that we create a somehow minimalist defconfig, i
> don't think using the 'monster' ubuntu defconfig (it has hundreds of
> drivers enabled....) makes too much sense for meta-ti. we used that
> because it was simpler for now, but I would hold on that patch until
> we have a simpler config. in fact we have already a config in the tree
> called omap4plus_defconfig, we will base on that one instead.

Ok, I'm fine with that - we can work out a minimal config.


> also we should wait until we have GST and GFX up and running before
> merging the kernel, to avoid a couple of iterations.

I would prefer to have the new kernel ASAP for many reasons. There were 
several reports about 3.1 not booting for some people. So, resolving that 
before Yocto Project 1.3 is released, is quite important. Plus, this gets us 
aligned better with your current Ubuntu-based release. And we are now starting 
to see patches against the old 3.1 kernel - by moving everyone to newer 3.4 we 
avoid waisting people's time fixing and enhancing the old 3.1...

So, I'd vote to get the new kernel first and worry about GST and GFX later. Do 
you feel there will be extensive changes to the kernel recipe associated with 
those? A little bit of churn on the defconfig would be acceptable...

-- 
Denys


  reply	other threads:[~2012-10-12 21:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 19:26 [PATCH v2 1/6] linux-omap4: update to ti-ubuntu-3.4-1487.6 Enrico Butera
2012-10-12 19:26 ` [PATCH v2 2/6] libdrm: enable omap experimental api support Enrico Butera
2012-10-12 20:39   ` Nicolas Dechesne
2012-10-12 19:26 ` [PATCH v2 3/6] ti-firmware-ipu-dce: add binary version 1.6+120829+191835+git53cf578 Enrico Butera
2012-10-12 19:26 ` [PATCH v2 4/6] libdce: add version 1.6.5.3 Enrico Butera
2012-10-12 19:26 ` [PATCH v2 5/6] gstreamer: bbappend to use TI-patched versions needed for gst-plugin-ducati Enrico Butera
2012-10-12 19:26 ` [PATCH v2 6/6] gst-plugin-ducati: add latest git version Enrico Butera
2012-10-12 20:53 ` [PATCH v2 1/6] linux-omap4: update to ti-ubuntu-3.4-1487.6 Denys Dmytriyenko
2012-10-12 21:11   ` Nicolas Dechesne
2012-10-12 21:27     ` Denys Dmytriyenko [this message]
2012-10-13  0:34       ` Enrico
2012-10-12 22:47   ` Enrico

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=20121012212730.GE32601@denix.org \
    --to=denys@ti.com \
    --cc=meta-ti@yoctoproject.org \
    --cc=ndec13@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.