mvme147 status

mvme147 status

[Christoph Hellwig]

Hi Geert,

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.

Re: mvme147 status

[Geert Uytterhoeven]

Hi Kars, Christoph,

On Sun, Sep 11, 2016 at 7:49 PM, Kars de Jong <nacirrut@gmail.com> wrote:
> Op zondag 11 september 2016 heeft Christoph Hellwig <hch@infradead.org> 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?

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

Re: mvme147 status

[Christoph Hellwig]

On Mon, Sep 12, 2016 at 09:43:48AM +0200, Geert Uytterhoeven wrote:
> 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?

I'll convert it then, shouldn't be too much work.  Let's hope the
buildbot covers m68k..

Re: mvme147 status

[Geert Uytterhoeven]

On Mon, Sep 12, 2016 at 9:46 AM, Christoph Hellwig <hch@infradead.org> wrote:
> Let's hope the buildbot covers m68k..

Yes it does.

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

Re: mvme147 status

[Stephen N Chivers]

linux-m68k-owner@vger.kernel.org wrote on 09/12/2016 05:43:48 PM:

> From: Geert Uytterhoeven <geert@linux-m68k.org>
> To: Kars de Jong <nacirrut@gmail.com>
> Cc: Christoph Hellwig <hch@infradead.org>, "linux-m68k@lists.linux-
> m68k.org" <linux-m68k@vger.kernel.org>, Stephen N Chivers/AUS/CSC@CSC
> Date: 09/12/2016 05:43 PM
> Subject: Re: mvme147 status
> Sent by: linux-m68k-owner@vger.kernel.org
> 
> Hi Kars, Christoph,
> 
> On Sun, Sep 11, 2016 at 7:49 PM, Kars de Jong <nacirrut@gmail.com> 
wrote:
> > Op zondag 11 september 2016 heeft Christoph Hellwig 
<hch@infradead.org> 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@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 somethinglike 
that.
>                                 -- Linus Torvalds
> --
> To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: mvme147 status

[Kars de Jong]

2016-09-13 22:05 GMT+02:00 Stephen N Chivers <schivers@csc.com>:
> > Stephen, are you still using them?
>
> Yes, I am still using the Motorola MVME-167 boards.

Note that this is about the MVME-147, not 167. Those are completely
different hardware (for instance, NCR SCSI instead of WD).

Regards,

Kars.

Re: mvme147 status

[John Paul Adrian Glaubitz]

Hi Christoph!

On 09/11/2016 07:16 PM, Christoph Hellwig wrote:
> 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 would be very interested in doing that, probably with some assistance from
Geert. I'm interested in getting more involved into kernel development but I
have successfully submitted only two patches so far.

This task sounds like a low-hanging fruit though and since I actually have
a VME system among other 68k machines, I have also a personal interest to
keep this driver.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: mvme147 status

[Christoph Hellwig]

On Mon, Sep 12, 2016 at 09:46:47AM +0200, John Paul Adrian Glaubitz wrote:
> This task sounds like a low-hanging fruit though and since I actually have
> a VME system among other 68k machines, I have also a personal interest to
> keep this driver.

That sounds great.  Once you've ressurrected your system I'd be happy to
mentor you for the SCSI driver work.

Re: mvme147 status

[Geert Uytterhoeven]

Hi Adrian,

On Mon, Sep 12, 2016 at 9:46 AM, John Paul Adrian Glaubitz
<glaubitz@physik.fu-berlin.de> wrote:
> On 09/11/2016 07:16 PM, Christoph Hellwig wrote:
>> 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 would be very interested in doing that, probably with some assistance from
> Geert. I'm interested in getting more involved into kernel development but I
> have successfully submitted only two patches so far.
>
> This task sounds like a low-hanging fruit though and since I actually have
> a VME system among other 68k machines, I have also a personal interest to
> keep this driver.

Thanks a lot!

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

Re: mvme147 status

[Christoph Hellwig]

On Mon, Sep 12, 2016 at 09:46:47AM +0200, John Paul Adrian Glaubitz wrote:
> Hi Christoph!
> 
> On 09/11/2016 07:16 PM, Christoph Hellwig wrote:
> > 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 would be very interested in doing that, probably with some assistance from
> Geert. I'm interested in getting more involved into kernel development but I
> have successfully submitted only two patches so far.

Did yo get any chance to look into this project?  My offer for help
still stands, but I'd like to make some progress on this issue.

Re: mvme147 status

[John Paul Adrian Glaubitz]

Hi Christoph!

On Mon, Jun 19, 2017 at 03:52:27AM -0700, Christoph Hellwig wrote:
> > I would be very interested in doing that, probably with some assistance from
> > Geert. I'm interested in getting more involved into kernel development but I
> > have successfully submitted only two patches so far.
> 
> Did yo get any chance to look into this project?  My offer for help
> still stands, but I'd like to make some progress on this issue.

Sorry, it somehow fell off the table. I'll try to look at it this
weekend if that's still ok.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: mvme147 status

[Christoph Hellwig]

On Mon, Jun 19, 2017 at 05:17:04PM +0200, John Paul Adrian Glaubitz wrote:
> Sorry, it somehow fell off the table. I'll try to look at it this
> weekend if that's still ok.

Sure, it's not _that_ urgent.

Re: mvme147 status

[John Paul Adrian Glaubitz]

On Mon, Jun 19, 2017 at 08:19:58AM -0700, Christoph Hellwig wrote:
> On Mon, Jun 19, 2017 at 05:17:04PM +0200, John Paul Adrian Glaubitz wrote:
> > Sorry, it somehow fell off the table. I'll try to look at it this
> > weekend if that's still ok.
> 
> Sure, it's not _that_ urgent.

I'm starting to work on this now and will get back to you once I run
into any issues. Thanks a lot for your patience!

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913