linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: cavokz@gmail.com (Domenico Andreoli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] Add support for generic BCM SoC chipsets
Date: Tue, 13 Nov 2012 22:31:21 +0100	[thread overview]
Message-ID: <20121113213121.GA14229@glitch> (raw)
In-Reply-To: <50A28920.7040805@broadcom.com>

On Tue, Nov 13, 2012 at 09:53:36AM -0800, Christian Daudt wrote:
> On 12-11-12 09:15 AM, Stephen Warren wrote:
...
> >I don't really have too strong of a preference. If the eventual intent
> >is for the directory to host all ARM Broadcom SoCs, then mach-bcm seems
> >reasonable.
> >
> Ok, sounds like sticking to mach-bcm has sufficient acks. What I was
> thinking of doing is, once mach-bcm had been introduced, to propose
> to pull in the 476x and 2835 into also, to do some consolidation.
> And have the separate files can keep separate owners - we'd just
> have Kconfig + Makefile shared most likely.

ok also for me

>  Or not. Ultimately I don't mind keeping 2835 and 476x as separate
> mach- either. Those are v6 SoCs, and at this point I have no plans
> on working on mobile v6 SoCs, only v7 onwards. So we can also say
> that mach-bcm is for v7+ SoCs and v6 SoCs keep their existing mach-
> dirs for now.

bcm476x is a non-existent directory yet so I'll be happy to switch to
mach-bcm at the next round (*).

thanks,
Domenico

(*) I'm a bit late with it because I've been distracted by a crazy way
to track kernel regressions I'm hacking on.  it's an experiment to test
a few ideas: http://filibusta.crema.unimi.it/~cavok/kbts/. early comments
are very welcome.

  reply	other threads:[~2012-11-13 21:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-11 14:57 [PATCH v2] Add support for generic BCM SoC chipsets Christian Daudt
2012-11-11 15:53 ` Florian Fainelli
2012-11-11 17:32   ` Christian Daudt
2012-11-11 18:43     ` Florian Fainelli
2012-11-11 21:40     ` Stephen Warren
2012-11-12 15:00       ` Arnd Bergmann
2012-11-12 16:04         ` Domenico Andreoli
2012-11-12 17:05           ` Arnd Bergmann
2012-11-12 17:15             ` Stephen Warren
2012-11-13 17:53               ` Christian Daudt
2012-11-13 21:31                 ` Domenico Andreoli [this message]
2012-11-12 15:17 ` Russell King - ARM Linux
2012-11-13 17:58   ` Christian Daudt
2012-11-13  4:45 ` Stephen Warren
2012-11-13 19:02   ` Christian Daudt

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=20121113213121.GA14229@glitch \
    --to=cavokz@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).