linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Adrian Bunk <bunk@stusta.de>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add Kconfig dependency !VT for VIOCONS
Date: Tue, 10 Oct 2006 21:35:10 -0700	[thread overview]
Message-ID: <20061010213510.c095cf2e.rdunlap@xenotime.net> (raw)
In-Reply-To: <20061011043006.GF721@stusta.de>

On Wed, 11 Oct 2006 06:30:06 +0200 Adrian Bunk wrote:

> On Tue, Oct 10, 2006 at 09:08:58PM -0700, Randy Dunlap wrote:
> > On Wed, 11 Oct 2006 05:56:29 +0200 Adrian Bunk wrote:
> > 
> > > On Tue, Oct 10, 2006 at 09:10:04AM -0700, Randy Dunlap wrote:
> > > > On Tue, 10 Oct 2006 06:55:34 +0200 Adrian Bunk wrote:
> > > > 
> > > > > On Fri, Oct 06, 2006 at 02:34:37PM -0700, Randy Dunlap wrote:
> > > > > > On Fri, 6 Oct 2006 13:00:07 -0700 Judith Lebzelter wrote:
> > > > > > 
> > > > > > > Actually, this gets rid of the CONFIG_VIOCONS from my .config, but 
> > > > > > > then I get another warning when I build:
> > > > > > > 
> > > > > > > Warning! Found recursive dependency: VT VIOCONS VT
> > > > > > > 
> > > > > > > Can anyone suggest something?
> > > > > > 
> > > > > > I think that your patch is mostly good/correct, but one more line
> > > > > > is needed on the VT side:  a deletion.
> > > > > > 
> > > > > > This works for me:
> > > > > > 
> > > > > > From: Randy Dunlap <rdunlap@xenotime.net>
> > > > > > 
> > > > > > Make allmodconfig .config build successfully by making VIOCONS
> > > > > > available only if VT=n.  VT need not check VIOCONS.
> > > > > > 
> > > > > > Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
> > > > > > ---
> > > > > >  arch/powerpc/platforms/iseries/Kconfig |    2 +-
> > > > > >  drivers/char/Kconfig                   |    1 -
> > > > > >  2 files changed, 1 insertion(+), 2 deletions(-)
> > > > > > 
> > > > > > --- linux-2619-rc1g2.orig/arch/powerpc/platforms/iseries/Kconfig
> > > > > > +++ linux-2619-rc1g2/arch/powerpc/platforms/iseries/Kconfig
> > > > > > @@ -3,7 +3,7 @@ menu "iSeries device drivers"
> > > > > >  	depends on PPC_ISERIES
> > > > > >  
> > > > > >  config VIOCONS
> > > > > > -	tristate "iSeries Virtual Console Support (Obsolete)"
> > > > > > +	tristate "iSeries Virtual Console Support (Obsolete)" if !VT
> > > > > >  	help
> > > > > >...
> > > > > >  config VT
> > > > > >  	bool "Virtual terminal" if EMBEDDED
> > > > > 
> > > > > With this dependency on EMBEDDED, you could as well simply remove 
> > > > > VIOCONS...
> > > > > 
> > > > > >  	select INPUT
> > > > > > -	default y if !VIOCONS
> > > > > 
> > > > > Removing the "default y" is wrong.
> > > > 
> > > > Oops, yes, agreed.
> > > > 
> > > > I don't see a way (using: make ARCH=powerpc iseries_defconfig,
> > > > which wants to enable VIOCONS) to prevent VT from being enabled
> > > > so that VIOCONS can be enabled.
> > > 
> > > With iseries_defconfig, CONFIG_VT is not enabled.
> > > 
> > > > However, since VIOCONS is marked (Obsolete) and since the powerpc
> > > > people don't comment on this patch & problem, maybe Judith is the
> > > > only person who cares.
> > > 
> > > allmodconfig turns on CONFIG_EMBEDDED.
> > 
> > So am I doing this incorrectly?
> > 
> > $ make ARCH=powerpc iseries_defconfig
> > 
> > $editor .config
> > 
> > CONFIG_VT=y
> > ...
> > #
> > # iSeries device drivers
> > #
> > CONFIG_VIODASD=y
> > CONFIG_VIOCD=m
> > CONFIG_VIOTAPE=m
> > CONFIG_VIOPATH=y
> 
> CONFIG_VIOCONS is not enabled.

Yep.  That was with my patch.
But I see what you mean.  Thanks.

---
~Randy

      reply	other threads:[~2006-10-11  4:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06 18:05 [PATCH] Add Kconfig dependency !VT for VIOCONS Judith Lebzelter
2006-10-06 20:00 ` Judith Lebzelter
2006-10-06 21:34   ` Randy Dunlap
2006-10-10  4:55     ` Adrian Bunk
2006-10-10 16:10       ` Randy Dunlap
2006-10-11  3:56         ` Adrian Bunk
2006-10-11  4:08           ` Randy Dunlap
2006-10-11  4:30             ` Adrian Bunk
2006-10-11  4:35               ` Randy Dunlap [this message]

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=20061010213510.c095cf2e.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).