public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "T Michael Turney" <tmike@theptrgroup•com>
To: <linuxppc-dev@ozlabs•org>
Subject: 2.4 kernel ppc-405 query
Date: Wed, 22 Sep 2004 14:00:07 -0700	[thread overview]
Message-ID: <GEEKLLHMFHLAJOBEEELHKEJJCLAA.tmike@theptrgroup.com> (raw)


Folks,
Most of my PPC experience is with Freescale pieces.

I have downloaded 2.4.26 from kernel.org as well
as 2.4.22 and the penguinppc patches for 2.4.22.

Currently working with penguinppc 2.4.22 on custom hardware.

Q.1) 405 platform seems more vulnerable to OOPS from config changes than
8xx?

General observation is the 405 code base seems more "fragile" than 8xx/8xxx
codebase.

Q.2) Is IDE internal workings different during discovery than FS accesses?

System can identify an IDE harddisk with 2 partitions but then generate
OOPS later on when attempting to mount /root filesystem.  I am suspecting
initial device setup including interrupt but don't want to waste time if
the discovery process indicates a fully-functional ide sub-system.

Cheers,
T.mike

             reply	other threads:[~2004-09-22 21:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-22 21:00 T Michael Turney [this message]
2004-09-23  2:12 ` 2.4 kernel ppc-405 query Jon Masters

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=GEEKLLHMFHLAJOBEEELHKEJJCLAA.tmike@theptrgroup.com \
    --to=tmike@theptrgroup$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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