LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: linuxppc-dev@ozlabs.org
Subject: build problems with powerpc allmodconfig
Date: Tue, 31 Oct 2006 15:22:13 +0100	[thread overview]
Message-ID: <20061031142213.GA9275@lst.de> (raw)

When trying to build an allmodconfig kernel on powerpc I run into
three errors, all related to the integeration of iseries support
into the main kernel image:

 - vicocons.c can't be compiled at the same time as CONFIG_VT, but
   instead of expressing that in the Kconfig it errors out in that
   case.  This should at least be a Kconfig dependency, but long
   term viocons must work at the same time as the normal vt code
   to have a single ppc64 image
 - vioscsi linkage fails because iseries_vscsi.c and rpa_vscsi.c.
   This needs some trivial indirection via function vectors, but
   how can we find out which one to use from the driver?  Both
   seem to look the same in the device tree
 - arch/powerpc/platforms/iseries/setup.c references rd_size
   when CONFIG_INITRD is set.  But rd_size is defined drivers/block/rd.c
   which can me modular (and is selected by CONFIG_BLK_DEV_RAM).
   This same bug is repeated in the arm amd arm26 code, but except
   for those no one outside of rd.c uses this symbol.  I don't see
   a point why arch code should modify this as it's already big enough.

             reply	other threads:[~2006-10-31 14:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-31 14:22 Christoph Hellwig [this message]
2006-10-31 15:22 ` build problems with powerpc allmodconfig Stephen Rothwell
2006-10-31 15:24   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2006-11-07 18:09 Judith Lebzelter
2006-11-08  0:58 ` Stephen Rothwell

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=20061031142213.GA9275@lst.de \
    --to=hch@lst.de \
    --cc=linuxppc-dev@ozlabs.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