linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dmalek@jlc.net>
To: bsimon@ctam.com.au
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: mpc8xx-2.3.10 configuration questions.
Date: Wed, 15 Sep 1999 15:28:02 -0400	[thread overview]
Message-ID: <37DFF342.94EE3B8@jlc.net> (raw)
In-Reply-To: 37DEF583.3DC2F0D4@ctam.com.au


Brendan Simon wrote:

> 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.

The cpu isn't too slow, so don't select this one.

> * MS-DOS, VFAT filesystems.
> * SMB network filesystems.

These are the result of generic VM changes and are not at all
related to 8xx.  You can't build them on any PPC machine in that
release.


> 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 has all been corrected in later releases.  I don't think any
of it was 8xx related as I didn't specifically change anything.

> .....This worries me a bit,
> especially having 8xx and 6xx cpus both defined.  Is this intentional ?

Well, you can either worry or fix it and get on with life.  Keep in
mind that the 8xx is really a minimal change to the Linux/PPC baseline.
If something doesn't work on the 8xx, and it is not specific to
the 8xx (like the file system stuff), chances are it doesn't work
for any PPC release.  Build it for a PMAC or something (you do have
some other PPC besides the 8xx, right?) and compare the results.
Remember, the 2.3.x CVS is a serious development tree, changing
every minute, and can go for many releases without running
properly in many aspects.  When you play in this sandbox you have
to expect things not to work correctly, and contribute to the
updates.

People have full multi-user, multiple network, PPP, web server
stuff running on 8xx platforms....and I never saw them post a
message to any of the PPC lists.....unfortunately no code updates
were posted either....


	-- Dan

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

  reply	other threads:[~1999-09-15 19:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-15  1:25 mpc8xx-2.3.10 configuration questions Brendan Simon
1999-09-15 19:28 ` Dan Malek [this message]
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=37DFF342.94EE3B8@jlc.net \
    --to=dmalek@jlc.net \
    --cc=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 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).