From: Eugene Surovegin <ebs@ebshome.net>
To: Stephen Winiecki <stevewin@us.ibm.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Configuring PCI w/ 44x
Date: Tue, 2 May 2006 16:49:16 -0700 [thread overview]
Message-ID: <20060502234916.GB25045@gate.ebshome.net> (raw)
In-Reply-To: <OF7EB5CFE4.CBC11341-ON87257162.0071F2FC-85257162.0072FFA5@us.ibm.com>
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
prev parent reply other threads:[~2006-05-02 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 20:58 Configuring PCI w/ 44x Stephen Winiecki
2006-05-02 23:49 ` 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=20060502234916.GB25045@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).