linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Brendan Simon <bsimon@ctam.com.au>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: mpc8xx-2.3.10 configuration questions.
Date: Thu, 16 Sep 1999 09:48:21 +1000	[thread overview]
Message-ID: <37E03044.9653F5D2@ctam.com.au> (raw)
In-Reply-To: 37DFF342.94EE3B8@jlc.net


Dan Malek wrote:

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

No, unfortunately I do not have access to a powermac.  My x86 laptop is just
about getting to the end of it's warranty and I am looking at upgrading in the
next month or so.  Since I have no desire to run DOS/Windows programs AND the
powerpc G3/G4 machines kick ass, I will probably upgrade to a PowerBook :)


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

I do expect things not to work.  I do not know the kernel internals very well
and I am not confident in changing things willy nilly.  Reporting things to
the mailing list seems reasonable to me to see if others have seen similar
things and have found solutions.  I don't mind getting my hands dirty and
trying things but I would rather wait for some direction from others first so
I don't head down the wrong track and possibly stuff up something that didn't
really have a problem.

In a previous email you mentioned that the embedded-2.2.5 release is still the
most stable, but you recommended to me that the 2.3.10 kernels are the place
to start for new ports.  I think I will do the port for the 2.2.5 first and
then migrate it to the 2.3.x stuff later.  Does this sound reasonable ?

Brendan Simon.

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

  reply	other threads:[~1999-09-15 23:48 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
1999-09-15 23:48   ` Brendan Simon [this message]
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=37E03044.9653F5D2@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 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).