From: Aubin LaBrosse <arl8778@rit.edu>
To: Michael Clark <michael@metaparadigm.com>
Cc: 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 19:45:05 -0400 [thread overview]
Message-ID: <1086997505.15798.8.camel@lhosts> (raw)
In-Reply-To: <40C9CC65.5030209@metaparadigm.com>
On Fri, 2004-06-11 at 11:14, Michael Clark wrote:
> On 06/11/04 21:13, Aubin LaBrosse wrote:
> > Hello all,
> >
> > I'm having a little fun with my first embedded system - it's an
> > Intrinsyc CerfCube, http://www.intrinsyc.com/products/cerfcube405EP/
> >
> > basically it's got an ibm 405ep powerpc processor in it. the thing
> > ships with a version of 2.4.21 but i've decided to take the newer
> > kernels for a spin on it. except i can't compile unless i enable pci,
> > which is unnecessary for this thing since it has no pci bus.
>
> Then why does it have a miniPCI connector?
so it does....I'm retarded. ;-)
Although I should still be able to build the kernel without pci support,
shouldn't I?
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..
-Aubin
> ~mc
next prev parent reply other threads:[~2004-06-11 23:45 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 [this message]
2004-06-12 1:23 ` Eugene Surovegin
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=1086997505.15798.8.camel@lhosts \
--to=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