From: akuster <akuster@dslextreme.com>
To: Pete Smithers <petesmithers@mail.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: redwood5
Date: Fri, 16 Aug 2002 10:58:07 -0700 [thread overview]
Message-ID: <3D5D3D2F.5090900@dslextreme.com> (raw)
In-Reply-To: 20020816171017.28307.qmail@mail.com
Pete Smithers wrote:
> hi
>
> i am trying to build a kernel from linuxppc_2_4_devel for the redwood5 board.
> there seems to have been some restructuring in that tree after which nobody probably compiled a kernel for that board. at least, when i select gpio, onchip ethernet, onchip ide or sicc serial port i get a bunch of errors, like
> ibm_ocp_gpio.c:124: `DCRN_CHCR0' undeclared (first use in this function) etc.
>
> from a naive point of view, the fix, at least for this particular error would be to #include asm/ibm403.h and above that one of the headers in arch/ppc/platforms that #define DCRN_CHCR_BASE, depending on the selected processor.
>
> but i don't think ibm_ocp_gpio.c should care about the selected processor, there must be some other way, to do that in a more generic way, so the other files that currently fail to compile won't fail anymore as well :)
>
> i am just too new to the ppc stuff, so i am asking you gurus what you would preferably do to fix the problem...
>
>
> Greets,
> Pete
>
>
>
Pete,
Please use the redwood5_config to start with( make redwood5_config).
The stb04xxx does not have a ocp ethernet. The gpio driver will not
work on any stbxxxx processors since most of the other devices such as
video, sound and other drivers you get from IBM use many gpio pins so
having a generic gpio driver make no sense. If you want to use the gpio
driver then you will need to update some of the ibmstb4.x files and the
driver.
Armin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-08-16 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-16 17:10 redwood5 Pete Smithers
2002-08-16 17:58 ` akuster [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=3D5D3D2F.5090900@dslextreme.com \
--to=akuster@dslextreme.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=petesmithers@mail.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).