* Re: sym53c875 in 2.4.2
[not found] <19350125130851.8098@mailhost.mipsys.com>
@ 2001-03-07 12:32 ` Geert Uytterhoeven
2001-03-07 15:27 ` Benjamin Herrenschmidt
0 siblings, 1 reply; 6+ messages in thread
From: Geert Uytterhoeven @ 2001-03-07 12:32 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: Linux/PPC Development
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/
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: sym53c875 in 2.4.2
2001-03-07 12:32 ` sym53c875 in 2.4.2 Geert Uytterhoeven
@ 2001-03-07 15:27 ` Benjamin Herrenschmidt
0 siblings, 0 replies; 6+ messages in thread
From: Benjamin Herrenschmidt @ 2001-03-07 15:27 UTC (permalink / raw)
To: Geert Uytterhoeven; +Cc: Linux/PPC Development, paulus
>> 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?
Right, I'll look into this. Could you, on your side, figure out why they
weren't
setup properly ? The hose resource code is new (Paulus), I didn't yet dive in
it's gory details and it works fine on pmacs.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* sym53c875 in 2.4.2
@ 2001-03-02 18:51 Geert Uytterhoeven
2001-03-04 2:19 ` Tom Rini
0 siblings, 1 reply; 6+ messages in thread
From: Geert Uytterhoeven @ 2001-03-02 18:51 UTC (permalink / raw)
To: Linux/PPC Development
Hi,
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.
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/
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: sym53c875 in 2.4.2
2001-03-02 18:51 Geert Uytterhoeven
@ 2001-03-04 2:19 ` Tom Rini
2001-03-05 0:30 ` Tom Rini
0 siblings, 1 reply; 6+ messages in thread
From: Tom Rini @ 2001-03-04 2:19 UTC (permalink / raw)
To: Geert Uytterhoeven; +Cc: Linux/PPC Development
On Fri, Mar 02, 2001 at 07:51:21PM +0100, Geert Uytterhoeven 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.
Er, the very current 2_4? Paulus just commited some changes which boil down
to we have phys_to_bus (or so) and can use the stock driver.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: sym53c875 in 2.4.2
2001-03-04 2:19 ` Tom Rini
@ 2001-03-05 0:30 ` Tom Rini
2001-03-05 8:22 ` Stefano Coluccini
0 siblings, 1 reply; 6+ messages in thread
From: Tom Rini @ 2001-03-05 0:30 UTC (permalink / raw)
To: Geert Uytterhoeven; +Cc: Linux/PPC Development
On Sat, Mar 03, 2001 at 07:19:20PM -0700, Tom Rini wrote:
>
> On Fri, Mar 02, 2001 at 07:51:21PM +0100, Geert Uytterhoeven 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.
>
> Er, the very current 2_4? Paulus just commited some changes which boil down
> to we have phys_to_bus (or so) and can use the stock driver.
And, the 2_4/2_5 merged tree i've got locally and will be pushing into 2_5
shortly works w/ my 53c895 anyways (Booted and got 3 disks on 2 buses).
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: sym53c875 in 2.4.2
2001-03-05 0:30 ` Tom Rini
@ 2001-03-05 8:22 ` Stefano Coluccini
0 siblings, 0 replies; 6+ messages in thread
From: Stefano Coluccini @ 2001-03-05 8:22 UTC (permalink / raw)
To: Tom Rini, Geert Uytterhoeven; +Cc: Linux/PPC Development
> > > 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.
> >
> > Er, the very current 2_4? Paulus just commited some changes
> which boil down
> > to we have phys_to_bus (or so) and can use the stock driver.
>
> And, the 2_4/2_5 merged tree i've got locally and will be pushing into 2_5
> shortly works w/ my 53c895 anyways (Booted and got 3 disks on 2 buses).
I have a 2_5 kernel, a Motorola MVME5100 with a sym53c875 based SCSI board
and it works fine.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2001-03-07 15:27 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <19350125130851.8098@mailhost.mipsys.com>
2001-03-07 12:32 ` sym53c875 in 2.4.2 Geert Uytterhoeven
2001-03-07 15:27 ` 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
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).