Re: tmscsim update for Linux 2.2.18pre15?
On Wed, Oct 11, 2000 at 12:15:08AM +0200, Matthias Andree wrote: > On Tue, 10 Oct 2000, Kurt Garloff wrote: > > > Actually, 2.0e3 did include one rather important fix which solved the > > Uh. Fix? This sounds like working around very broken devices to me, or > are devices allowed to wreak havoc if sync negotiation is tried in spite > of not being advertised in inquiry data? Well, at least for devices that do not claim SCSI-2 compliance (but 1 or 1-CCS), it may not be that bad. > > I'll happily sent a patch against 2.4.0t9 and/or 2.2.18p15 to > > Linus/Alan to get an updated version included in the mainstream > > kernel. > > Sounds good. I'd prefered getting some feedback by them. Maybe, I should try just sending the patches out to them ... Regards, -- Kurt Garloff <[EMAIL PROTECTED]> [Eindhoven, NL] Physics: Plasma simulations <[EMAIL PROTECTED]> [TU Eindhoven, NL] Linux: SCSI, Security <[EMAIL PROTECTED]> [SuSE Nuernberg, FRG] (See mail header or public key servers for PGP2 and GPG public keys.) PGP signature
Re: tmscsim update for Linux 2.2.18pre15?
On Wed, Oct 11, 2000 at 12:15:08AM +0200, Matthias Andree wrote: On Tue, 10 Oct 2000, Kurt Garloff wrote: Actually, 2.0e3 did include one rather important fix which solved the Uh. Fix? This sounds like working around very broken devices to me, or are devices allowed to wreak havoc if sync negotiation is tried in spite of not being advertised in inquiry data? Well, at least for devices that do not claim SCSI-2 compliance (but 1 or 1-CCS), it may not be that bad. I'll happily sent a patch against 2.4.0t9 and/or 2.2.18p15 to Linus/Alan to get an updated version included in the mainstream kernel. Sounds good. I'd prefered getting some feedback by them. Maybe, I should try just sending the patches out to them ... Regards, -- Kurt Garloff [EMAIL PROTECTED] [Eindhoven, NL] Physics: Plasma simulations [EMAIL PROTECTED] [TU Eindhoven, NL] Linux: SCSI, Security [EMAIL PROTECTED] [SuSE Nuernberg, FRG] (See mail header or public key servers for PGP2 and GPG public keys.) PGP signature
Re: tmscsim update for Linux 2.2.18pre15?
On Tue, 10 Oct 2000, Kurt Garloff wrote: > Actually, 2.0e3 did include one rather important fix which solved the Uh. Fix? This sounds like working around very broken devices to me, or are devices allowed to wreak havoc if sync negotiation is tried in spite of not being advertised in inquiry data? > I'll happily sent a patch against 2.4.0t9 and/or 2.2.18p15 to > Linus/Alan to get an updated version included in the mainstream > kernel. Sounds good. Thanks a lot! PGP signature
Re: tmscsim update for Linux 2.2.18pre15?
Kurt Garloff wrote: > Actually, 2.0e3 did include one rather important fix which solved the > trouble: Some devices get upset, when the driver tries to negotiate sync > (or wide) connections, but the device actually does not support it. > So, the driver now waits for the first INQUIRY result and parses the > relevant fields to determine, whether sync should be tried. > > As far as I can conclude from the reports I got since the 2.0e3 release (two > weeks ago), it solves the remaining issues. I believe I sent the successful report to Kurt, but just in case, the latest tmscsim driver from the web page worked just fine. In my case, it negotiated the sync transfer with the hard disks successfully while it didn't with the old async CD drive. Expected correct behavior. This is with 2.4.0-test9.(Oh, I think when I reported to Kurt, it was test9-prexxx, but it now works with test-9 on my PC.) I would like to thank Kurt for continueing to maintain the old tmscsim driver for the new kernel. Happy Hacking, Chiaki Ishikawa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: tmscsim update for Linux 2.2.18pre15?
On Tue, Oct 10, 2000 at 11:52:33AM +0200, Matthias Andree wrote: > On Mon, 02 Oct 2000, Alan Cox announced: > > 2.2.18pre15 > > I'd like to know if there are any issues with the current dc390-2.0e or > 2.0e3 drivers that prevent its inclusion/that prevent Kurt from > submitting it for inclusion. As per the web page, 2.0e was supposed to > be sent to Linux for 2.4, so it should not have been too bad ;) Right. 2.0e was supposed to be sent off, but unfortunately, some new error reports came up which I wanted to address. Then you run out of time because you have other projects and the thing gets lost. Actually, 2.0e3 did include one rather important fix which solved the trouble: Some devices get upset, when the driver tries to negotiate sync (or wide) connections, but the device actually does not support it. So, the driver now waits for the first INQUIRY result and parses the relevant fields to determine, whether sync should be tried. As far as I can conclude from the reports I got since the 2.0e3 release (two weeks ago), it solves the remaining issues. I'll happily sent a patch against 2.4.0t9 and/or 2.2.18p15 to Linus/Alan to get an updated version included in the mainstream kernel. Regards, -- Kurt Garloff <[EMAIL PROTECTED]> Eindhoven, NL GPG key: See mail header, key servers Linux kernel development SuSE GmbH, Nuernberg, FRG SCSI, Security PGP signature
tmscsim update for Linux 2.2.18pre15?
On Mon, 02 Oct 2000, Alan Cox announced: > 2.2.18pre15 I'd like to know if there are any issues with the current dc390-2.0e or 2.0e3 drivers that prevent its inclusion/that prevent Kurt from submitting it for inclusion. As per the web page, 2.0e was supposed to be sent to Linux for 2.4, so it should not have been too bad ;) AFAICS, the xmas-1998-release, 2.0d, is still in 2.2.18pre15, and I was under the impression it was reported to be incompatible with some SCSI scanners, until 2.0d18. (Of course, it might be useful to additionally blacklist non-compliant devices publicly so manufacturers have a motivation to fix their things). -- Matthias Andree - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: tmscsim update for Linux 2.2.18pre15?
On Tue, Oct 10, 2000 at 11:52:33AM +0200, Matthias Andree wrote: On Mon, 02 Oct 2000, Alan Cox announced: 2.2.18pre15 I'd like to know if there are any issues with the current dc390-2.0e or 2.0e3 drivers that prevent its inclusion/that prevent Kurt from submitting it for inclusion. As per the web page, 2.0e was supposed to be sent to Linux for 2.4, so it should not have been too bad ;) Right. 2.0e was supposed to be sent off, but unfortunately, some new error reports came up which I wanted to address. Then you run out of time because you have other projects and the thing gets lost. Actually, 2.0e3 did include one rather important fix which solved the trouble: Some devices get upset, when the driver tries to negotiate sync (or wide) connections, but the device actually does not support it. So, the driver now waits for the first INQUIRY result and parses the relevant fields to determine, whether sync should be tried. As far as I can conclude from the reports I got since the 2.0e3 release (two weeks ago), it solves the remaining issues. I'll happily sent a patch against 2.4.0t9 and/or 2.2.18p15 to Linus/Alan to get an updated version included in the mainstream kernel. Regards, -- Kurt Garloff [EMAIL PROTECTED] Eindhoven, NL GPG key: See mail header, key servers Linux kernel development SuSE GmbH, Nuernberg, FRG SCSI, Security PGP signature
Re: tmscsim update for Linux 2.2.18pre15?
Kurt Garloff wrote: Actually, 2.0e3 did include one rather important fix which solved the trouble: Some devices get upset, when the driver tries to negotiate sync (or wide) connections, but the device actually does not support it. So, the driver now waits for the first INQUIRY result and parses the relevant fields to determine, whether sync should be tried. As far as I can conclude from the reports I got since the 2.0e3 release (two weeks ago), it solves the remaining issues. I believe I sent the successful report to Kurt, but just in case, the latest tmscsim driver from the web page worked just fine. In my case, it negotiated the sync transfer with the hard disks successfully while it didn't with the old async CD drive. Expected correct behavior. This is with 2.4.0-test9.(Oh, I think when I reported to Kurt, it was test9-prexxx, but it now works with test-9 on my PC.) I would like to thank Kurt for continueing to maintain the old tmscsim driver for the new kernel. Happy Hacking, Chiaki Ishikawa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: tmscsim update for Linux 2.2.18pre15?
On Tue, 10 Oct 2000, Kurt Garloff wrote: Actually, 2.0e3 did include one rather important fix which solved the Uh. Fix? This sounds like working around very broken devices to me, or are devices allowed to wreak havoc if sync negotiation is tried in spite of not being advertised in inquiry data? I'll happily sent a patch against 2.4.0t9 and/or 2.2.18p15 to Linus/Alan to get an updated version included in the mainstream kernel. Sounds good. Thanks a lot! PGP signature
