From: David Woodhouse <dwmw2@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warnings after merge of the final tree (mtd tree related)
Date: Tue, 26 Oct 2010 09:51:48 +0100 [thread overview]
Message-ID: <1288083108.29264.14.camel@macbook.infradead.org> (raw)
In-Reply-To: <20101026134959.86b807d1.sfr@canb.auug.org.au>
On Tue, 2010-10-26 at 13:49 +1100, Stephen Rothwell wrote:
>
> I am not sure where these came from ...
It's a config issue. You have chosen to build NOR flash support.
NOR flash can be wired up many ways. It could be four 8-bit chips in
parallel in a 32-bit bus, two 16-bit chips in a 32-bit bus, 2 8-bit
chips in a 16-bit bus, one 16-bit chip in a 16-bus bus, etc...
You have elected to support *none* of those configurations. No NOR chip
support can work.
You don't get to choose individual geometry options unless you set
CONFIG_MTD_ADV_OPTIONS -- by default you get a fully versatile driver
which can cope with anything at runtime.
I'll build a ppc44x_defconfig and work out what's going wrong. I'd
expect this kind of thing with randconfig, but not a defconfig.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2010-10-26 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 2:49 linux-next: build warnings after merge of the final tree (mtd tree related) Stephen Rothwell
2010-10-26 8:51 ` David Woodhouse [this message]
2010-10-26 10:49 ` David Woodhouse
2010-10-26 16:43 ` H Hartley Sweeten
2010-10-26 16:48 ` David Woodhouse
2010-10-26 9:15 ` David Woodhouse
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=1288083108.29264.14.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).