From: Eugene Surovegin <ebs@ebshome.net>
To: Aubin LaBrosse <arl8778@rit.edu>
Cc: Michael Clark <michael@metaparadigm.com>,
linux-kernel@vger.kernel.org, benh@kernel.crashing.org
Subject: Re: [PPC] 2.6.7-rc3 IBM405EP kernel won't build without PCI
Date: Fri, 11 Jun 2004 18:23:37 -0700 [thread overview]
Message-ID: <20040612012337.GA8154@gate.ebshome.net> (raw)
In-Reply-To: <1086997505.15798.8.camel@lhosts>
On Fri, Jun 11, 2004 at 07:45:05PM -0400, Aubin LaBrosse wrote:
> Although I should still be able to build the kernel without pci support,
> shouldn't I?
Yes, correctly configured board port for 405EP can be build without PCI support.
> Where does the CONFIG_BIOS_FIXUP come from and is it necessary for a
> device like this is I guess what I'm asking - the code compiled in by
> CONFIG_BIOS_FIXUP seems to depend on PCI being in but you can select it
> without selecting PCI - that's the underlying issue here I think. I
> assume I don't really need CONFIG_BIOS_FIXUP for this device (given the
> name of the option, I would hope that this thing doesn't have a bios
> that needs 'fixing
> up') but I'm not even sure how to turn it off... and of course I'm only
> guessing based on the error I got and the names of the things involved,
> i haven't rolled up my sleeves and got into it yet..
Did you make board port yourself? The reason I'm asking is none of Linux PPC
trees has support for board you mentioned. So it's quite unlikely that Linux PPC
kernel can be used on your hardware as is.
.config file doesn't look correct, it enables support for EP405 board (Embedded
Plannet 405GP based board).
CONFIG_BIOS_FIXUP is set arch/ppc/platforms/4xx/Kcoonfig on per board basis.
Also, I'd recommend asking questions about 405EP on linuxppc-embedded list, not
here. This will increase probability of you getting some help :).
Eugene
prev parent reply other threads:[~2004-06-12 1:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 13:13 [PPC] 2.6.7-rc3 IBM405EP kernel won't build without PCI Aubin LaBrosse
2004-06-11 15:14 ` Michael Clark
2004-06-11 23:45 ` Aubin LaBrosse
2004-06-12 1:23 ` 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=20040612012337.GA8154@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=arl8778@rit.edu \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@metaparadigm.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