All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brendan Simon <bsimon@ctam.com.au>
To: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: mpc8xx-2.3.10 configuration questions.
Date: Wed, 15 Sep 1999 11:25:23 +1000	[thread overview]
Message-ID: <37DEF583.3DC2F0D4@ctam.com.au> (raw)


I have managed to compile a zImage for the BSE target.  Great.  It took
a lot of trial and error to find out which options to leave out.  The
serial and serial-console support is an obvious one which seems natural
to include but causes the build to fail.

It fails to build if I include any of the following options.  I can't
remember the exact error messages but can post them later if it helps.
* CPU is too slow to handle full bandwidth.
* MS-DOS, VFAT filesystems.
* SMB network filesystems.

Has anyone had similar problems ?  Must other options be included for
any of these to work ?

I notice that the .config file has both 8xx and 6xx cpus defined even
though I've chosen 8xx/860.  Similarly, CONFIG_PARIDE_PARPORT=y even
though I don't enable it.  It looks as though there are some defaults
that are set regardless of what the user sets.  This worries me a bit,
especially having 8xx and 6xx cpus both defined.  Is this intentional ?

Thanks,
Brendan Simon.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~1999-09-15  1:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-15  1:25 Brendan Simon [this message]
1999-09-15 19:28 ` mpc8xx-2.3.10 configuration questions Dan Malek
1999-09-15 23:48   ` Brendan Simon
1999-09-16 15:39     ` Dan Malek
1999-09-16  7:36   ` Graham Stoney
1999-09-16 15:32     ` Dan Malek
1999-09-17  0:48       ` Graham Stoney
1999-09-17  1:47         ` Dan Malek

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=37DEF583.3DC2F0D4@ctam.com.au \
    --to=bsimon@ctam.com.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.