From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: if i want powerpc "local bus" support, must i select CONFIG_FSL_LBC?
Date: Mon, 7 Dec 2015 13:04:27 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.20.1512071258010.8534@localhost> (raw)
trying to make a long story short, was handed an aging powerpc
MPC8360e system on which to place linux, along with a BSP that does in
fact generate a bootable kernel and filesystem. however, according to
this online page (and i am *not* in any way a powerpc expert):
http://cache.freescale.com/files/netcomm/doc/fact_sheet/MPC8360EFS.pdf
this processor has something called a "local bus", off of which on
this board hang things like DSP, FPGA and other things.
during boot, i can see absolutely no mention of any of the devices
attached to this local bus, or even that the bus itself is recognized,
then i noticed that the .config file used to build this 3.14.29 kernel
does not select what looks like the appropriate kernel option FSL_LBC.
if anyone out there is a powerpc expert, can you confirm that you
need to select that option (and hence compile in the source file
arch/powerpc/sysdev/fsl_lbc.c) to get that support?
i'm puzzled only because, if that file is required for local bus
support, the people who gave us the BSP really should have turned it
on.
thanks for any guidance.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
reply other threads:[~2015-12-07 18:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LFD.2.20.1512071258010.8534@localhost \
--to=rpjday@crashcourse.ca \
--cc=kernelnewbies@lists.kernelnewbies.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).