From: Richard Hirst <rhirst@levanta.com>
To: Kars de Jong <jongk@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, linux-scsi@vger.kernel.org,
Andi Kleen <ak@suse.de>, Matthew Wilcox <matthew@wil.cx>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: Removing BROKEN scsi drivers
Date: Wed, 5 Oct 2005 15:00:05 +0100 [thread overview]
Message-ID: <20051005140005.GD6490@levanta.com> (raw)
In-Reply-To: <1128519034.5063.10.camel@laptop-lcs.localdomain>
On Wed, Oct 05, 2005 at 03:30:33PM +0200, Kars de Jong wrote:
> On wo, 2005-10-05 at 13:32 +0100, Richard Hirst wrote:
> > On Wed, Oct 05, 2005 at 12:39:25PM +0100, Christoph Hellwig wrote:
> > > On Wed, Oct 05, 2005 at 05:31:08AM -0600, Matthew Wilcox wrote:
> > > > On Wed, Oct 05, 2005 at 01:14:32PM +0200, Andi Kleen wrote:
> > > > > SCSI_AMIGA7XX - no maintainer, broken forever
> > > > > MVME16x_SCSI - no maintainer, broken forever
> > > > > BVME6000_SCSI - same
> > > >
> > > > I don't think there's any point in deleting these. I'm not even sure
> > > > why they're marked BROKEN. They share 99% of their code with drivers
> > > > which are working. And I thought Richard Hirst was maintaining them ...
> > >
> > > They don't. All these use the broken and obsolete 53c7xx driver, not
> > > James new 53c700 core. The driver should be easy to reimplement based
> > > on the 53x700 for someone who has the hardware and cares about it.
> >
> > I never claimed to maintain the amiga stuff, but you are right that they
> > all use the 53c7xx driver that I originally created. The sensible thing
> > to do is to migrate those systems to use James 53c700 core, but it seems
> > wise to poll the linux-m68k list before removing them. I don't do much
> > with my VME hardware these days but I know there have been patches
> > posted for the serial driver recently so maybe someone has the scsi
> > working.
>
> I have at least the 53c7xx driver and the MVME16X driver working, the
> Amiga and BVME stuff is untested (but does compile).
Great :-)
> I patched the 53c7xx core to get it to work again, but the patch is ugly
> and uses some mid level SCSI driver internals, which it shouldn't. It's
> currently only present in the m68k CVS repository.
>
> Are you sure it's that easy to use the new 53c700 core? These boards all
> have 53c710 chips, and are quite some changes in the 53c7xx driver
> compared to the 53c8xx driver it originated from.
The 53c700 core code handles 53c710 as well, so it should be easy. Not
that I've actually tried..
Richard
next prev parent reply other threads:[~2005-10-05 14:00 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 11:14 Removing BROKEN scsi drivers Andi Kleen
2005-10-05 11:22 ` Arjan van de Ven
2005-10-05 11:31 ` Matthew Wilcox
2005-10-05 11:39 ` Christoph Hellwig
2005-10-05 12:32 ` Richard Hirst
2005-10-05 13:30 ` Kars de Jong
2005-10-05 14:00 ` Richard Hirst [this message]
2005-10-05 14:03 ` James Bottomley
2005-10-05 14:35 ` Rolf Eike Beer
2005-10-07 8:27 ` Geert Uytterhoeven
2005-10-07 13:42 ` Richard Hirst
2005-10-07 13:53 ` Kars de Jong
2005-11-15 9:51 ` Christoph Hellwig
2005-11-15 10:17 ` Ingo Juergensmann
2005-11-15 10:30 ` Christoph Hellwig
2005-11-15 11:32 ` Richard Hirst
2005-11-15 12:08 ` Roman Zippel
2005-11-15 12:11 ` Kars de Jong
2005-11-15 13:05 ` Matthew Wilcox
2005-11-22 8:36 ` Christoph Hellwig
2005-11-22 21:43 ` Kars de Jong
2005-11-22 22:20 ` Matthew Wilcox
2005-11-27 16:47 ` James Bottomley
2005-11-29 22:24 ` James Bottomley
2005-11-30 8:31 ` Kars de Jong
2005-11-30 8:45 ` Ingo Juergensmann
2005-12-01 20:43 ` Kars de Jong
2005-12-01 20:47 ` James Bottomley
2005-12-01 23:29 ` Richard Hirst
2005-12-02 15:03 ` Ingo Juergensmann
2005-12-07 21:25 ` Ingo Juergensmann
2006-07-07 12:44 ` Christoph Hellwig
2006-07-09 11:16 ` Richard Hirst
2006-07-09 11:25 ` Kars de Jong
2006-10-30 11:13 ` Christoph Hellwig
2006-10-30 12:34 ` Kars de Jong
2006-10-31 21:47 ` [RFC PATCH] m68k: switch to 53c700 driver Kars de Jong
2006-11-02 21:34 ` Geert Uytterhoeven
2006-12-17 22:28 ` James Bottomley
2006-12-18 9:34 ` Geert Uytterhoeven
2006-12-19 3:09 ` Al Viro
2006-12-22 21:21 ` Kars de Jong
2007-04-29 21:43 ` Christoph Hellwig
2005-10-05 11:43 ` Removing BROKEN scsi drivers Christoph Hellwig
2005-10-05 22:36 ` Douglas Gilbert
2005-10-06 10:23 ` Andi Kleen
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=20051005140005.GD6490@levanta.com \
--to=rhirst@levanta.com \
--cc=ak@suse.de \
--cc=hch@infradead.org \
--cc=jongk@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.