All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	"Aguirre, Sergio" <saaguirre@ti.com>,
	"Nagarajan, Rajkumar" <x0133774@ti.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"Hiremath, Vaibhav" <hvaibhav@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Alternative for defconfig
Date: Thu, 17 Jun 2010 17:23:21 +0300	[thread overview]
Message-ID: <20100617142321.GJ12255@atomide.com> (raw)
In-Reply-To: <20100616075642.GA12255@atomide.com>

* Tony Lindgren <tony@atomide.com> [100616 10:50]:
> * Felipe Contreras <felipe.contreras@gmail.com> [100611 19:03]:
> > On Fri, Jun 11, 2010 at 6:07 PM, Laurent Pinchart
> > <laurent.pinchart@ideasonboard.com> wrote:
> > > My understanding is that Linus will remove all ARM defconfigs in 2.6.36,
> > > unless someone can convince him not to.
> > 
> > Huh? I thought he was only threatening to remove them[1]. I don't
> > think he said he was going to do that without any alternative in
> > place.
> > 
> > My suggestion[2] was to have minimal defconfigs so that we could do
> > $ cp arch/arm/configs/omap3_beagle_baseconfig .config
> > $ echo "" | make ARCH=arm oldconfig
> > 
> > [1] http://article.gmane.org/gmane.linux.kernel/994194
> > [2] http://article.gmane.org/gmane.linux.kernel/995412
> 
> Sounds like the defconfigs will be going though and we'll use
> some Kconfig based system that's still open. I believe Russell
> said he is not taking any more defconfig patches, so we should
> not merge them either.
> 
> Anyways, we already have multi-omap mostly working for both
> mach-omap1 and mach-omap2.
> 
> So the remaining things to do are:
> 
> 1. For mach-omap1, patch entry-macro.S to allow compiling in
>    7xx, 15xx and 16xx. This can be done in a similar way as
>    for mach-omap2. The only issue is how to detect 7xx from
>    other mach-omap1 omaps. If anybody has a chance to work
>    on this, please go for it!

Have not done anything about this.
 
> 2. The old omap_cfg_reg mux function needs to disappear
>    for mach-omap2 and use the new mux code instead. I'm
>    currently working on this and should have it ready
>    for testing this week.

Got finally rid of these. These are in devel-mux branch
on top of the devel-tls branch.
 
> 3. To boot both ARMv6 and 7, we need to get rid of
>    CONFIG_HAS_TLS_REG. I already have a patch for that,
>    I'll try to update that during this week.

Need to still look at this, but a working version is in
devel-tls branch.
 
> 4. To make CONFIG_VFP work for both ARMv6 and 7, we need
>    to fix CONFIG_VFPv3 so it boots on ARMv6 too. It currently
>    oopses. Will take a look at this after I'm done with the
>    CONFIG_HAS_TLS_REG. This is another one where some help
>    would be nice. To reproduce, boot Linux on ARMv6 with
>    CONFIG_VFPv3 set.

Got this fixed, but need to still test. Also in devel-tls
branch.

Regards,

Tony

  reply	other threads:[~2010-06-17 14:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09  9:51 [PATCH] OMAP: V4L2: Enable V4L2 on ZOOM2/3 & 3630SDP Nagarajan, Rajkumar
2010-06-09 10:27 ` Laurent Pinchart
2010-06-09 10:32   ` Hiremath, Vaibhav
2010-06-11 12:19   ` Alternative for defconfig Nagarajan, Rajkumar
2010-06-11 13:43     ` Felipe Contreras
2010-06-11 14:55       ` Aguirre, Sergio
2010-06-11 15:07         ` Laurent Pinchart
2010-06-11 15:12           ` Aguirre, Sergio
2010-06-11 15:14           ` Gadiyar, Anand
2010-06-11 15:26             ` Laurent Pinchart
2010-06-11 15:28               ` Aguirre, Sergio
2010-06-11 15:35             ` Sid Boyce
2010-06-11 16:09           ` Felipe Contreras
2010-06-16  7:56             ` Tony Lindgren
2010-06-17 14:23               ` Tony Lindgren [this message]
2010-06-18 13:00               ` Felipe Contreras

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=20100617142321.GJ12255@atomide.com \
    --to=tony@atomide.com \
    --cc=felipe.contreras@gmail.com \
    --cc=hvaibhav@ti.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=saaguirre@ti.com \
    --cc=x0133774@ti.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.