Re: scsi and PS2 mode parallel port programming
On Fri, Jan 12, 2001 at 10:41:29AM +, Nick Hibma wrote: You've been speaking to Nicolas Souchu, right? He has written the current driver and seems to know a fair bit about this topic. We've solved the problem. Nick | I'll put this on my pile of things to and dig through the CAM changes to | find it. There weren't that many in the past year. I finally heard from the guy who noticed the change, and asked if he could help localize it. | I don't know much about the PS2 mode nor the parallel port driver | (allthough I've had my fingers in there, as you know). A parallel port in ECP mode should support PS2 without any problem, correct? And if I recall, it worked under 3.x, so that *should* rule out a buggy BIOS or hardware anomaly. I *hate* when problems only afflict my machine. jcm -- o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o | Jonathon McKitrick ~ | | "I prefer the term 'Artificial Person' myself." | o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o -- Qube Software, Ltd. Private: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message -- [EMAIL PROTECTED] Alcve - Open Source Software Engineer - http://www.alcove.fr To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: scsi and PS2 mode parallel port programming
You've been speaking to Nicolas Souchu, right? He has written the current driver and seems to know a fair bit about this topic. Nick | I'll put this on my pile of things to and dig through the CAM changes to | find it. There weren't that many in the past year. I finally heard from the guy who noticed the change, and asked if he could help localize it. | I don't know much about the PS2 mode nor the parallel port driver | (allthough I've had my fingers in there, as you know). A parallel port in ECP mode should support PS2 without any problem, correct? And if I recall, it worked under 3.x, so that *should* rule out a buggy BIOS or hardware anomaly. I *hate* when problems only afflict my machine. jcm -- o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o | Jonathon McKitrick ~ | | "I prefer the term 'Artificial Person' myself." | o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o -- Qube Software, Ltd. Private: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
scsi and PS2 mode parallel port programming
Greets to everyone, I'm new to hackers, but I'm trying to tackle a couple of bugs in the parallel port zip driver under newbus/4.x. I was able to fix the big one (nibble mode didn't work at all) so now I am trying to get PS2 mode working, which is much faster on reads. I have 2 questions: 1. Is anyone familiar with PS2 transfer protocols with a parallel port set in ECP mode? It could always be a buggy BIOS, but I cannot get PS2 mode to work on my laptop with pport set to ECP mode. But it works in standard bi-directional mode. 2. In the list of scsi error codes, 0x00 is no error, and the defacto errors start with 0x02. However, in PS2 mode, when asked for status, the zip drive returns 0x01. If I ignore any byte with this bit set, the drive seems to work okay, but this is a crude and potentially risky fix. Is there any way to find out what this actually means? Could it just be a stray bit? Or is it an additional scsi status that should be handled? I *believe* PS2 mode quit working for parallel port zips after a commit to the cam/scsi system Dec 1999, but I am not familiar with that code, so I didn't know where to start looking. I am very interested in contributing my meager skills to the BSD effort in this manner, but I need a little help getting pointed in the right direction. Thanks in advance for any help anyone can offer. jcm -- o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o | Jonathon McKitrick ~ | | "I prefer the term 'Artificial Person' myself." | o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: scsi and PS2 mode parallel port programming
2. In the list of scsi error codes, 0x00 is no error, and the defacto errors start with 0x02. However, in PS2 mode, when asked for status, the zip drive returns 0x01. If I ignore any byte with this bit set, the drive seems to work okay, but this is a crude and potentially risky fix. Is there any way to find out what this actually means? Could it just be a stray bit? Or is it an additional scsi status that should be handled? I *believe* PS2 mode quit working for parallel port zips after a commit to the cam/scsi system Dec 1999, but I am not familiar with that code, so I didn't know where to start looking. Could you point a date (or date range) when that commit to CAM was? I'm vaguely familiar with it and more than willing to help. Where does the 0x01 come from? From the drive or from the drivers? I am very interested in contributing my meager skills to the BSD effort in this manner, but I need a little help getting pointed in the right direction. Thanks in advance for any help anyone can offer. -hackers is probably the best place for these questions if you want to try and find a person with the necessary skills. Nick -- Qube Software, Ltd. Private: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: scsi and PS2 mode parallel port programming
| Could you point a date (or date range) when that commit to CAM was? I'm | vaguely familiar with it and more than willing to help. I can *try*, but it was someone else who spotted the changes, and I can't seem to contact him. But he also did not find a specific change. I can give it a shot, but I would guess it has to do with handling the scsi status codes. | Where does the 0x01 come from? From the drive or from the drivers? Directly from the drive. The imm module asks the drive itself if it has any more status to return, and it returns the 0x01 value. Also, have you ever gotten r_dtr to work in PS2 mode? All I ever get is 0x01 returned, never any valid data, even though the negociate routine says PS2 is working an accepted. jcm -- o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o | Jonathon McKitrick ~ | | "I prefer the term 'Artificial Person' myself." | o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: scsi and PS2 mode parallel port programming
I can *try*, but it was someone else who spotted the changes, and I can't seem to contact him. But he also did not find a specific change. I can give it a shot, but I would guess it has to do with handling the scsi status codes. I'll put this on my pile of things to and dig through the CAM changes to find it. There weren't that many in the past year. | Where does the 0x01 come from? From the drive or from the drivers? Directly from the drive. The imm module asks the drive itself if it has any more status to return, and it returns the 0x01 value. Also, have you ever gotten r_dtr to work in PS2 mode? All I ever get is 0x01 returned, never any valid data, even though the negociate routine says PS2 is working an accepted. I don't know much about the PS2 mode nor the parallel port driver (allthough I've had my fingers in there, as you know). Nick -- Qube Software, Ltd. Private: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: scsi and PS2 mode parallel port programming
| I'll put this on my pile of things to and dig through the CAM changes to | find it. There weren't that many in the past year. I finally heard from the guy who noticed the change, and asked if he could help localize it. | I don't know much about the PS2 mode nor the parallel port driver | (allthough I've had my fingers in there, as you know). A parallel port in ECP mode should support PS2 without any problem, correct? And if I recall, it worked under 3.x, so that *should* rule out a buggy BIOS or hardware anomaly. I *hate* when problems only afflict my machine. jcm -- o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o | Jonathon McKitrick ~ | | "I prefer the term 'Artificial Person' myself." | o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
