linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Monro <davidm@amberdata.demon.co.uk>
To: Linux/ppc Dev List <linuxppc-dev@lists.linuxppc.org>
Subject: prep problems - a couple of questions
Date: Wed, 23 Aug 2000 07:07:34 +0100	[thread overview]
Message-ID: <39A36A26.1291926E@amberdata.demon.co.uk> (raw)


Hi,

I'm encountering a couple of problems with 2.4.0-test3+ on PReP systems.
I've finally traced the major one down to the following: calling
request_region() in prep_setup_arch() causes the machine to stop.
Tracing it a little deeper, it is the call to kmalloc() inside
request_region() which actually fails. I'm guessing this is caused by
the changes to the slab allocator in 2.4.0-test3.

So it looks like we can't afford to call request_region() this early in
the game. Can anybody tell me when it is first safe to use it?

Secondly, once I hacked around that I discovered that the IDE acesses
are all coming out byteswapped (this includes the ID strings etc, not
just the data). This is caused by the addition of the '#if 0' in
include/asm-ppc/ide.h as follows:

#if 0
#undef insw
#define insw(port, buf, ns)     do {                            \
        ppc_ide_md.insw((port), (buf), (ns));                   \
} while (0)

#undef outsw
#define outsw(port, buf, ns)    do {                            \
        ppc_ide_md.outsw((port), (buf), (ns));                  \
} while (0)
#endif

This appears in 2.3.99-pre6. Anybody know why? If I take out the #if 0
the IDE drives work fine again...


Cheers,

	David

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

             reply	other threads:[~2000-08-23  6:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-23  6:07 David Monro [this message]
2000-08-23 11:58 ` prep problems - a couple of questions Geert Uytterhoeven

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=39A36A26.1291926E@amberdata.demon.co.uk \
    --to=davidm@amberdata.demon.co.uk \
    --cc=linuxppc-dev@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).