From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Troy Benjegerdes <hozer@drgw.net>
Cc: Alois Fertl <alois_fertl@talknet.de>,
LinuxppcDev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: ncr810 problem on powerstack
Date: Fri, 19 Jan 2001 08:54:15 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.05.10101190851170.27117-100000@callisto.of.borg> (raw)
In-Reply-To: <20010119000309.A17347@altus.drgw.net>
On Fri, 19 Jan 2001, Troy Benjegerdes wrote:
> On Tue, Jan 16, 2001 at 09:44:07PM +0100, Alois Fertl wrote:
> > I tried the recent 2.4.1-pre1 kernel on a powerstack but the ncr810 based
> > SCSI code does not work. The driver complains about CACHE INCORRECTLY CONFIGURED.
> >
> > Anybody knows what this comes from. Attached if the full boot log of the system.
>
> Arrrgh, the same thing happens on my powerstack.
> I'd track this down, but
>
> a) I don't have time
> b) the machine is my mail server and runs the linuxppc_2_2 tree happily.
I saw a similar thing on my LongTrail (with '875 card) after I added a call to
pci_assign_unassigned_resources() to arch/ppc/kernel/pci.c (like PReP) did, and
before I fixed the test for ppc_md.pcibios_enable_device_hook.
Perhaps PReP doesn't like ppc_md.pcibios_enable_device_hook instead of
pci_assign_unassigned_resources?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-19 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 20:44 ncr810 problem on powerstack Alois Fertl
2001-01-19 6:03 ` Troy Benjegerdes
2001-01-19 7:54 ` Geert Uytterhoeven [this message]
2001-02-18 20:26 ` Alois Fertl
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=Pine.LNX.4.05.10101190851170.27117-100000@callisto.of.borg \
--to=geert@linux-m68k.org \
--cc=alois_fertl@talknet.de \
--cc=hozer@drgw.net \
--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).