linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ruedi.Hofer@ascom.ch
To: linuxppc-embedded@lists.linuxppc.org
Cc: kernel@linux01.hasler.ascom.ch
Subject: Re: Mvista Kernel on FADS 860
Date: Thu, 06 Jul 2000 16:46:59 +0100 (CED)	[thread overview]
Message-ID: <0FXA0064T6EGQK@pmdf-it.hasler.ascom.ch> (raw)

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1158 bytes --]

Although I know that FADS is a bad choice, some more info concerning this problem:
(I have no solution yet)

I'm referring to hardhat 1.1, kernel source 2.2.13.7.

In several files (eg include/asm-ppc/mpc8xx.h) I found lines containing
#ifdef CONFIG_FADS
...
#endif
Therefore I think I should be able to configure FADS somewhere in the kernel config menu.
Unfortunately, I am not!

All my trials failed of adding the #define to the file arch/ppc/config.in. Example:
  choice 'Machine Type' \
        "PowerMac       CONFIG_PMAC \
         PReP/MTX       CONFIG_PREP \
         CHRP           CONFIG_CHRP \
         PowerMac/PReP/CHRP     CONFIG_ALL_PPC \
         APUS           CONFIG_APUS \
         MBX            CONFIG_MBX \
         RPXL           CONFIG_RPXLITE \
         RPXC           CONFIG_RPXCLASSIC \
         EST8xx         CONFIG_EST8xx \
***         FADS           CONFIG_FADS \
         BSE-IP         CONFIG_BSEIP" PowerMac


Any ideas?

/Ruedi



PS: I even have a problem compiling the newly installed hardhat kernel 2.2.13.7. (Without
changing anything, just typing make dep && make zImage!)
I get 'FEC_INTERRUPT'  undeclared in fec.c!

             reply	other threads:[~2000-07-06 15:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-06 15:46 Ruedi.Hofer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-07-04 15:55 Mvista Kernel on FADS 860 Ruedi.Hofer

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=0FXA0064T6EGQK@pmdf-it.hasler.ascom.ch \
    --to=ruedi.hofer@ascom.ch \
    --cc=kernel@linux01.hasler.ascom.ch \
    --cc=linuxppc-embedded@lists.linuxppc.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).