linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: Stephen Winiecki <stevewin@us.ibm.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Fw: Configuring PCI w/ 44x
Date: Wed, 3 May 2006 10:18:01 -0700	[thread overview]
Message-ID: <20060503171801.GB32503@gate.ebshome.net> (raw)
In-Reply-To: <OF417BCEEB.CBCC9EBC-ON87257163.005DB572-85257163.005E34EB@us.ibm.com>

On Wed, May 03, 2006 at 01:11:26PM -0400, Stephen Winiecki wrote:
> 
> Eugene Surovegin <ebs@ebshome.net> wrote on 05/02/2006 07:49:16 PM:
> 
> > On Tue, May 02, 2006 at 04:58:32PM -0400, Stephen Winiecki wrote:
> > > I have a question regarding configuring PCI with 44x.  Using 2.6.17-rc3
> as
> > > a reference, PCI_CONFIG is defined for the 44x defconfigs, and Kconfig
> is
> > > not enabled to reflect/change the setting for 44x.  When I update
> > > arch/ppc/Kconfig to enable configuring or not configuring PCI with 44x,
> and
> > > then don't configure it, the kernel won't compile:
> >
> > Hmm, you cannot disable PCI for 44x in the current 2.6. It's always
> > enabled.
> >
> > If you changed Konfig to be able to do so, why are you complaining
> > here? It's not enough to just change Konfig, you have to modify Ocotea
> > port as well. Look for example how this is handled for 85xx.
> >
> > Patches are welcome.
> >
> > --
> > Eugene
> >
> 
> I was first wondering if for some reason defaulting/forcing PCI to always
> be configured for 44x was intentional.

Yes. I think it's quite obvious from the way it's configured in 
Konfig.

>  I was second reporting the fact
> that if a change is made to not configure PCI for 44x, the kernel will not
> compile.

Well, I don't follow you here. You made the wrong change and report 
here that it broke the build. How is this interesting?

Your report looked as you discovered a bug, when in fact you broke the 
build yourself.

And again, if disabling PCI is important to you you are welcome to 
submit patches instead of sending misleading e-mails to this list.

-- 
Eugene

      reply	other threads:[~2006-05-03 17:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 17:11 Fw: Configuring PCI w/ 44x Stephen Winiecki
2006-05-03 17:18 ` Eugene Surovegin [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=20060503171801.GB32503@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=stevewin@us.ibm.com \
    /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).