From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM: mvebu: minor Armada 370 RD improvements
Date: Thu, 11 Sep 2014 16:40:40 +0200 [thread overview]
Message-ID: <20140911144040.GC29780@lunn.ch> (raw)
In-Reply-To: <20140911142655.GB30828@titan.lakedaemon.net>
> > Since debian does modular builds on a regular basis, maybe they have
> > some recommendations.
> >
> > My thought is that I doubt we're the only SoC family with this issue.
> > To avoid the maintenance headache of extra _mod_defconfig's, perhaps we
> > could add a ./scripts/config toggle to turn the current .config enabled
> > tristates into modules?
As Thomas pointed out, that is probably the easy bit. We need a test
system which has access to these modules, and udev in order to get
them loaded. Do any of the current boot farms support this?
What might be possible is to work on top of the new test initiative,
kicked off at the last summit. That is going to need a more capable
rootfs, so might provide a usable basis. We also need some tests, so
that once we have finished booting, do we at least have all the
devices we expect in /sys. That would of at least found the recent SPI
FLASH breakage.
Andrew
next prev parent reply other threads:[~2014-09-11 14:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 9:56 [PATCH 0/4] ARM: mvebu: minor Armada 370 RD improvements Thomas Petazzoni
2014-09-11 9:56 ` [PATCH 1/4] ARM: mvebu: add gpio fan support to Armada 370 RD Thomas Petazzoni
2014-09-11 9:56 ` [PATCH 2/4] ARM: mvebu: add user LED support of " Thomas Petazzoni
2014-09-11 9:56 ` [PATCH 3/4] ARM: mvebu: add LED class support built-in in mvebu_v7_defconfig Thomas Petazzoni
2014-09-11 9:56 ` [PATCH 4/4] ARM: mvebu: add gpio-fan to mvebu_v7_defconfig Thomas Petazzoni
2014-09-11 13:43 ` [PATCH 0/4] ARM: mvebu: minor Armada 370 RD improvements Andrew Lunn
2014-09-11 14:00 ` Thomas Petazzoni
2014-09-11 14:26 ` Jason Cooper
2014-09-11 14:26 ` Jason Cooper
2014-09-11 14:40 ` Andrew Lunn [this message]
2014-09-11 15:24 ` Ian Campbell
2014-09-13 21:27 ` Jason Cooper
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=20140911144040.GC29780@lunn.ch \
--to=andrew@lunn.ch \
--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