From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: sym53c875 in 2.4.2
Date: Wed, 7 Mar 2001 13:32:57 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.05.10103071330410.773-100000@callisto.of.borg> (raw)
In-Reply-To: <19350125130851.8098@mailhost.mipsys.com>
On Fri, 2 Mar 2001, Benjamin Herrenschmidt wrote:
> >I just tried the current bk linuxppc_2_4 on my CHRP LongTrail with Sym53c875
> >card. The Sym53c8xx driver fails downloading the SCSI scripts, and keeps
> >trying
> >ad infinitum.
> >
> >At first sight, the kernel seems to work when I disable the Sym53c8xx driver
> >with `sym53c8xx=excl:0x1400'. It boots to a shell from the MESH.
> >
> >PCI seems to be OK. Only changes are that the sl82c105 IDE got assigned some
> >I/O ports now.
> >
> >Everything worked fine in the 2.4.1 from a month ago.
>
> Are there any conflicting assignements ? Could you check if the new
> phys_to_bus() function returns proper values (finds the bus on which
> the Sym chip resides) ?
My hose resources were not set up, so phys_to_bus() returned NULL. Wouldn't it
be better to return pa in that case, or at least print an error to the console?
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 parent reply other threads:[~2001-03-07 12:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19350125130851.8098@mailhost.mipsys.com>
2001-03-07 12:32 ` Geert Uytterhoeven [this message]
2001-03-07 15:27 ` sym53c875 in 2.4.2 Benjamin Herrenschmidt
2001-03-02 18:51 Geert Uytterhoeven
2001-03-04 2:19 ` Tom Rini
2001-03-05 0:30 ` Tom Rini
2001-03-05 8:22 ` Stefano Coluccini
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.10103071330410.773-100000@callisto.of.borg \
--to=geert@linux-m68k.org \
--cc=benh@kernel.crashing.org \
--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).