From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: Heads up: Linus plans to kill ARM defconfigs
Date: Fri, 4 Jun 2010 03:37:10 +0200 [thread overview]
Message-ID: <201006040337.10593.marek.vasut@gmail.com> (raw)
In-Reply-To: <AANLkTinEq99_8UyVNnmzNEreDoyHKEnxpuJmaAo_kpPN@mail.gmail.com>
Dne P? 4. ?ervna 2010 03:35:28 Eric Miao napsal(a):
> On Fri, Jun 4, 2010 at 9:16 AM, Ryan Mallon <ryan@bluewatersys.com> wrote:
> > Marek Vasut wrote:
> >> Dne P? 4. ?ervna 2010 01:33:35 Ryan Mallon napsal(a):
> >>> Nicolas Pitre wrote:
> >>>> On Fri, 4 Jun 2010, Ryan Mallon wrote:
> >>>>> Is it worth being a bit proactive and getting rid of some of them in
> >>>>> advance? Things like spear3[012]0_defconfig are basically identically
> >>>>> except for the board type. Combining all three of those would remove
> >>>>> 1500 lines of code.
> >>>>
> >>>> Please go ahead with a patch.
> >>>
> >>> Hmm, not as easy as I thought. The three boards cannot be built into a
> >>> single kernel since the arch/arm/mach-spear3xx/spear3[012]0.c files all
> >>> extern a bunch of structs which have naming conflicts.
> >>>
> >>> It does look possible to rewrite that code so that all three boards can
> >>> be built into a single kernel. I can try and put together a patch, but
> >>> I don't have any hardware to test with.
> >>>
> >>> The at91 is actually in a similar state, where only one of the
> >>> at91sam9260, at91sam9g45, etc can be selected. Again, it should be
> >>> possible to rework the code so that most of the different cpus can be
> >>> built into a single kernel. I'm sure other mach's are in a simliar
> >>> state. Fixing these where possible would allow us to have single
> >>> defconfigs per mach directory and reduce code churn, which is what
> >>> Linus is really complaining about.
> >>
> >> I just tested, PXA (mach-pxa) probably can be compiled into single
> >> kernel supporting all the boards.
> >
> > Yes, IIRC Russell and Eric did a huge amount of work to get pxa into
> > that state.
> >
> > ryan at okiwi:configs$ grep "ARCH_PXA=y" * | wc -l
> > 25
> >
> > Can we remove/combine some of those?
>
> Definitely. In the end of the day, I would like to see pxa_defconfig only.
> But at the moment, I need every board maintainer to review their defconfig
> and combine them as much as possible. E.g.
>
> palmte_defconfig palmtt_defconfig palmz71_defconfig palmz72_defconfig
This is OMAP stuff, not PXA. But yeah, these could be combined. I don't have
these devices available at the moment (and it might be a problem getting them
into operational state).
>
> I'd guess can simply combine into one. (Marek, feel free to do it)
>
> I'd more like a step to step work instead of a brutely removal of all
> defconfig, not sure if Linus is going to buy in.
>
> For those sub-arch which cannot simply compile a single kernel for multiple
> boards, s5p* as previously mentioned, I suggest not to introduce any new
> defconfig until the problem is solved.
>
> Also, we are now working on a single kernel for multiple sub-arch (at least
> what Nicolas and I am doing now, and welcome to join us). It's tough (the
> way to handle different phys_offset is only the tip of the iceberg) and
> seems now more and more necessary. so hopefully by the end of the day, we
> may possible end up with only very few defconfig.
How long is your day now ?
next prev parent reply other threads:[~2010-06-04 1:37 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 19:24 Heads up: Linus plans to kill ARM defconfigs Russell King - ARM Linux
2010-06-03 19:55 ` Marek Vasut
2010-06-03 20:01 ` Russell King - ARM Linux
2010-06-03 20:27 ` Marek Vasut
2010-06-03 20:38 ` Nicolas Pitre
2010-06-08 14:41 ` Russell King - ARM Linux
2010-06-03 23:46 ` Daniel Walker
2010-06-04 11:06 ` Uwe Kleine-König
2010-06-03 19:59 ` Nicolas Pitre
2010-06-03 20:03 ` Russell King - ARM Linux
2010-06-03 20:36 ` Nicolas Pitre
2010-06-03 21:04 ` Ryan Mallon
2010-06-03 22:31 ` Nicolas Pitre
2010-06-03 23:33 ` Ryan Mallon
2010-06-03 23:45 ` Kyungmin Park
2010-06-04 0:13 ` Nicolas Pitre
2010-06-04 1:10 ` Marek Vasut
2010-06-04 1:16 ` Ryan Mallon
2010-06-04 1:35 ` Eric Miao
2010-06-04 1:37 ` Marek Vasut [this message]
2010-06-04 1:50 ` Marek Vasut
2010-06-04 1:53 ` Marek Vasut
2010-06-04 6:03 ` Tony Lindgren
2010-06-04 14:59 ` Cory Maccarrone
2010-06-07 7:41 ` Tony Lindgren
2010-06-04 1:57 ` Eric Miao
2010-06-04 6:10 ` Tony Lindgren
2010-06-04 7:12 ` Eric Miao
2010-06-04 8:40 ` Martin Guy
2010-06-04 20:51 ` Nicolas Pitre
2010-06-04 22:08 ` Krzysztof Halasa
2010-06-08 11:58 ` Russell King - ARM Linux
2010-06-08 12:31 ` Tony Lindgren
2010-06-08 12:43 ` Eric Miao
2010-06-08 12:49 ` Russell King - ARM Linux
2010-06-08 13:00 ` Eric Miao
2010-06-08 12:43 ` David John
2010-06-08 12:44 ` Eric Miao
2010-06-08 12:50 ` Nicolas Pitre
2010-06-08 12:44 ` Nicolas Pitre
2010-06-08 12:50 ` Russell King - ARM Linux
2010-06-08 13:01 ` Nicolas Pitre
2010-06-08 13:13 ` Russell King - ARM Linux
2010-06-08 14:51 ` Eric Miao
2010-06-08 16:55 ` Nicolas Pitre
2010-06-08 23:23 ` Daniel Walker
2010-06-08 12:50 ` Christer Weinigel
2010-06-08 13:10 ` Russell King - ARM Linux
2010-06-08 20:51 ` Ryan Mallon
2010-06-08 21:22 ` Russell King - ARM Linux
2010-06-08 21:32 ` Ryan Mallon
2010-06-08 23:02 ` Nicolas Pitre
2010-06-08 23:21 ` Ryan Mallon
2010-06-08 23:26 ` Daniel Walker
2010-06-08 23:31 ` Nicolas Pitre
2010-06-08 23:52 ` Ryan Mallon
2010-06-09 0:14 ` Nicolas Pitre
2010-06-09 6:07 ` Hendrik Sattler
2010-06-09 13:32 ` Daniel Walker
2010-06-10 6:32 ` Uwe Kleine-König
2010-06-10 19:18 ` Nicolas Pitre
2010-06-09 21:56 ` Ryan Mallon
2010-06-25 12:36 ` Catalin Marinas
2010-06-07 21:09 ` Ryan Mallon
2010-06-04 10:42 ` Tony Lindgren
2010-06-04 8:36 ` pieterg
[not found] ` <AANLkTilyIb8WDAanNHlQKHco6rSjzNjNS9Q3TpWQqt8o@mail.gmail.com>
2010-06-04 8:42 ` Eric Miao
2010-06-04 8:56 ` Daniel Mack
2010-06-04 9:37 ` pieterg
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=201006040337.10593.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).