Re: mvme147 status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



linux-m68k-owner@xxxxxxxxxxxxxxx wrote on 09/12/2016 05:43:48 PM:

From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
To: Kars de Jong <nacirrut@xxxxxxxxx>
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, "linux-m68k@lists.linux-
m68k.org" <linux-m68k@xxxxxxxxxxxxxxx>, Stephen N Chivers/AUS/CSC@CSC
Date: 09/12/2016 05:43 PM
Subject: Re: mvme147 status
Sent by: linux-m68k-owner@xxxxxxxxxxxxxxx

Hi Kars, Christoph,

On Sun, Sep 11, 2016 at 7:49 PM, Kars de Jong <nacirrut@xxxxxxxxx> 
wrote:
Op zondag 11 september 2016 heeft Christoph Hellwig 
<hch@xxxxxxxxxxxxx> het
volgende geschreven:
do you know what the status of the mvme147 board support / SCSI 
driver
is?  The mvme147 scsi driver is one of the few remaining drivers 
still
using the scsi_module infrastructure thay I'd like to finally kill 
off.

Unlike some other drivers it should be fairly trivial to convert, but
I'd like to first know if there is any point in investing that work.

I still have some MVME147 hardware, but I haven't run anything more 
recent
than 2.6 kernels on it. I doubt anyone is still using it.

Are there still other users of the chipset driver?  Does 
CONFIG_MVME147

The wd33c93 chipset driver is also used on various Amigas and on SGI 
MIPS
systems. Those no longer use scsi_module, though (IIRC I converted most 
of
them in 2009).

still build?

Of course it does ;-)

I personally don't have a big issue with just killing the board 
support
code, it can always be revived when needed.

Killing board support doesn't gain us that much...

Stephen, are you still using them?

Yes, I am still using the Motorola MVME-167 boards.

They are operated without disks (boot from a NFS file server). They 
currently
run kernel 2.6.24 as a baseline.

Support for the serial console (serial167) on the MVME-167 board was 
dropped in
linux 2.6.37.

I have experimented with later kernel versions (up to and including 3.17) 
and have a revised device
driver for the serial console (now called mvme167x_scc) as the original 
one was
dropped around 2.6.37 kernel. The new console driver works without 
problems
but I have never submitted the patches. Geert has seen a version of them 
but
I haven't had the time to continue the work as my day job has been very 
intense
for about two years.

I do not have any SCSI disks for them, although I might be able to cobble
something together using some old SUN-4 disks we have here. The big 
problem
is the SCSI cable from the "transition" module at the back of the VME rack
to SCSI enclosure.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- 
geert@xxxxxxxxxxxxxx

In personal conversations with technical people, I call myself a hacker. 
But
when I'm talking to journalists I just say "programmer" or somethinglike 
that.
                                -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Video for Linux]     [Yosemite News]     [Linux S/390]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux