From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Gabor Juhos <juhosg@openwrt.org>, Felix Fietkau <nbd@openwrt.org>,
Ralf Baechle <ralf@linux-mips.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
"kaloz@openwrt.org" <kaloz@openwrt.org>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
Cliff Holden <Cliff.Holden@Atheros.com>
Subject: Re: [PATCH 03/18] MIPS: add generic support for multiple machines within a single kernel
Date: Tue, 23 Nov 2010 10:49:19 -0800 [thread overview]
Message-ID: <20101123184919.GJ29396@tux> (raw)
In-Reply-To: <AANLkTikMwNqd507sPSTQOXt4KYkr9v61H=4_ESo7xFdj@mail.gmail.com>
On Tue, Nov 23, 2010 at 10:29:49AM -0800, Arnaud Lacombe wrote:
> Hi,
>
> On Tue, Nov 23, 2010 at 10:06 AM, Gabor Juhos <juhosg@openwrt.org> wrote:
> > This patch adds a generic solution to support multiple machines based on
> > a given SoC within a single kernel image. It is implemented already for
> > several other architectures but MIPS has no generic support for that yet.
> >
> Is this the way `arch/mips' wants to go to support multiple machine
> within a same kernel image ? Flattened Device Tree is the other way to
> achieve that. I remind the latter being proposed by Felix Fietkau on
> #openwrt.
We either do this now or later. If now it means more work and we'd have
to wait until the work is done. If no one is working on it right now
it seems easier to submit this as is for now and later get the port
done to the device tree model.
Luis
next prev parent reply other threads:[~2010-11-23 18:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 15:06 [PATCH 00/18] MIPS: initial support for the Atheros AR71XX/AR724X/AR913X SoCs Gabor Juhos
2010-11-23 15:06 ` [PATCH 01/18] MIPS: add initial support for the Atheros AR71XX/AR724X/AR931X SoCs Gabor Juhos
2010-11-23 15:06 ` [PATCH 02/18] MIPS: ath79: add GPIOLIB support Gabor Juhos
2010-11-23 15:06 ` [PATCH 03/18] MIPS: add generic support for multiple machines within a single kernel Gabor Juhos
2010-11-23 18:29 ` Arnaud Lacombe
2010-11-23 18:49 ` Luis R. Rodriguez [this message]
2010-11-23 18:51 ` Gabor Juhos
2010-11-23 19:06 ` Felix Fietkau
2010-11-23 19:20 ` David Daney
2010-11-23 22:12 ` Ralf Baechle
2010-11-23 15:06 ` [PATCH 04/18] MIPS: ath79: utilize the MIPS multi-machine support Gabor Juhos
2010-11-23 15:06 ` [PATCH 05/18] MIPS: ath79: add initial support for the Atheros PB44 reference board Gabor Juhos
2010-11-23 15:06 ` [PATCH 06/18] MIPS: ath79: add common GPIO LEDs device Gabor Juhos
2010-11-23 15:06 ` [PATCH 07/18] watchdog: add driver for the Atheros AR71XX/AR724X/AR913X SoCs Gabor Juhos
2010-11-23 15:06 ` [PATCH 08/18] MIPS: ath79: add common watchdog device Gabor Juhos
2010-11-23 15:06 ` [PATCH 09/18] input: add input driver for polled GPIO buttons Gabor Juhos
2010-11-23 19:24 ` Ben Gardiner
2010-11-24 17:24 ` Ben Gardiner
2010-11-24 18:54 ` Gabor Juhos
2010-11-24 20:28 ` Ben Gardiner
2010-11-28 8:31 ` Dmitry Torokhov
2010-11-23 15:06 ` [PATCH 10/18] MIPS: ath79: add common GPIO buttons device Gabor Juhos
2010-11-23 15:06 ` [PATCH 11/18] spi: add SPI controller driver for the Atheros AR71XX/AR724X/AR913X SoCs Gabor Juhos
2010-11-23 15:06 ` [PATCH 12/18] MIPS: ath79: add common SPI controller device Gabor Juhos
2010-11-23 15:06 ` [PATCH 13/18] USB: ehci: add workaround for Synopsys HC bug Gabor Juhos
2010-11-23 15:06 ` [PATCH 14/18] USB: ehci: add bus glue for the Atheros AR71XX/AR724X/AR913X SoCs Gabor Juhos
2010-11-23 15:06 ` [PATCH 15/18] USB: ohci: add bus glue for the Atheros AR71XX/AR7240 SoCs Gabor Juhos
2010-11-23 15:06 ` [PATCH 16/18] MIPS: ath79: add common USB Host Controller device Gabor Juhos
2010-11-23 15:06 ` [PATCH 17/18] MIPS: ath79: add initial support for the Atheros AP81 reference board Gabor Juhos
2010-11-23 15:06 ` [PATCH 18/18] MIPS: ath79: add common WMAC device for AR913X based boards Gabor Juhos
2010-11-23 18:16 ` [PATCH 00/18] MIPS: initial support for the Atheros AR71XX/AR724X/AR913X SoCs Arnaud Lacombe
2010-11-23 18:18 ` Arnaud Lacombe
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=20101123184919.GJ29396@tux \
--to=lrodriguez@atheros.com \
--cc=Cliff.Holden@Atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=juhosg@openwrt.org \
--cc=kaloz@openwrt.org \
--cc=lacombar@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=nbd@openwrt.org \
--cc=ralf@linux-mips.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