[parisc-linux] SCSI in arch/{m68k,parisc,sparc*}/config.in

[parisc-linux] SCSI in arch/{m68k,parisc,sparc*}/config.in

[Keith Owens]

cc: kaos@ocs.com.au please, I am not on these lists.

arch/{m68k,parisc,sparc*}/config.in have their own SCSI list instead of
using drivers/scsi/Config.in.  Cleaning up the SCSI config file is on
my 2.5 TODO list, can you tell me why these architectures have their
own list of SCSI devices?

If it is because only some SCSI drivers work on these architectures, do
you really need to be this specific?  Other architectures source
drivers/scsi/Config.in without checking for arch dependent drivers.  If
the need is to support extra arch specific drivers, use the same
technique as acorn :-

# drivers/scsi/Config.in
if [ "$CONFIG_ARCH_ACORN" = "y" ]; then
   source drivers/acorn/scsi/Config.in
fi

ps. There is no entry for parisc in MAINTAINERS.

Re: [parisc-linux] SCSI in arch/{m68k,parisc,sparc*}/config.in

[Jes Sorensen]

>>>>> "Keith" == Keith Owens <kaos@ocs.com.au> writes:

Keith> cc: kaos@ocs.com.au please, I am not on these lists.
Keith> arch/{m68k,parisc,sparc*}/config.in have their own SCSI list
Keith> instead of using drivers/scsi/Config.in.  Cleaning up the SCSI
Keith> config file is on my 2.5 TODO list, can you tell me why these
Keith> architectures have their own list of SCSI devices?

Keith> If it is because only some SCSI drivers work on these
Keith> architectures, do you really need to be this specific?  Other
Keith> architectures source drivers/scsi/Config.in without checking
Keith> for arch dependent drivers.  If the need is to support extra
Keith> arch specific drivers, use the same technique as acorn :-

For the m68k it's because we do not support any PCI/ISA devices and
all the SCSI drivers in drivers/scsi/Config.in at least used to not be
protected by CONFIG_ISA, CONFIG_PCI etc. hence we would end up with
200 questions about SCSI drivers that do not work. If you can convince
Linus to take a patch that puts CONFIG_{ISA,PCI,SBUS,NUBUS,ZORRO} in
drivers/scsi/Config.in then we can move it no problem.

Jes

[parisc-linux] Re: SCSI in arch/{m68k,parisc,sparc*}/config.in

[Geert Uytterhoeven]

On Fri, 22 Jun 2001, Keith Owens wrote:
> cc: kaos@ocs.com.au please, I am not on these lists.
> 
> arch/{m68k,parisc,sparc*}/config.in have their own SCSI list instead of
> using drivers/scsi/Config.in.  Cleaning up the SCSI config file is on
> my 2.5 TODO list, can you tell me why these architectures have their
> own list of SCSI devices?
> 
> If it is because only some SCSI drivers work on these architectures, do
> you really need to be this specific?  Other architectures source
> drivers/scsi/Config.in without checking for arch dependent drivers.  If
> the need is to support extra arch specific drivers, use the same
> technique as acorn :-

[ speaking for m68k ]

We do that to avoid being annoyed with questions about irrelevant SCSI
hardware. If nowadays all ISA/EISA/MCA/PCI SCSI hardware questions are properly
protected with their respective CONFIG_*, we're willing to include the generic
drivers/scsi/Config.in.

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

[parisc-linux] Re: SCSI in arch/{m68k,parisc,sparc*}/config.in

[David S. Miller]

Keith Owens writes:
 > arch/{m68k,parisc,sparc*}/config.in have their own SCSI list instead of
 > using drivers/scsi/Config.in.  Cleaning up the SCSI config file is on
 > my 2.5 TODO list, can you tell me why these architectures have their
 > own list of SCSI devices?
 > 
 > If it is because only some SCSI drivers work on these architectures, do
 > you really need to be this specific?

If I can forward every "How come I can compile ISA SCSI device X and
it doesn't work on my UltraSPARC" email to you, I'll more than happily
start including drivers/scsi/Config.in :-)

Jeff Garzik and I just did all the necessary dep_tristate'ing for
drivers/net/Config.in and at least in my tree I include in on sparc64.

Being able to do this on every platform is certainly a goal, and for
all the PCI drivers to be portable enough to work on every platform is
the next step.  I think Jeff and I can do it for the networking
drivers, but I have no idea who would go about working on this for
the scsi stuff.

Later,
David S. Miller
davem@redhat.com

[parisc-linux] Re: SCSI in arch/{m68k,parisc,sparc*}/config.in

[Keith Owens]

On Fri, 22 Jun 2001 17:32:13 -0700 (PDT), 
"David S. Miller" <davem@redhat.com> wrote:
>If I can forward every "How come I can compile ISA SCSI device X and
>it doesn't work on my UltraSPARC" email to you, I'll more than happily
>start including drivers/scsi/Config.in :-)

ESR has already done much of the bus dependency checking for SCSI in
CML2.  We don't plan to do anything about 2.4, it is a 2.5 cleanup.  I
just wanted to confirm why some architectures had their own SCSI list,
that has now been confirmed.