It seems Brian Feldman wrote: >> It seems Brian Feldman wrote: >> > Yes, I finally got it working! The explanation is in the patch, which I >> > should >> > not need to explain again :) >> >> Hmm, Does it not work as is ?? It works on my LS120 drive, and a couble >> of others. Besides your hack doesn't find my ZIP drive, and makes it >> fail miserably. > >In that case, I'll fix it to do a strstr or something like that. What's >your ZIP drive say?
Have to get home to power up the sucker first, but if below doesn't work on all systems, it will still break on the ZIP then.. >> If its just that you are unsatisfied with only max 32K transfers, thats >> another matter, and stuff for later changes. > >No, it does not work at all with that maximum set. I'm using the disk to hold >an FFS filesystem, and mounting it, BTW. See, in the old driver, it limited >the transfer, but it ALSO queued the rest of the transfer. AFD doesn't, and >I can tell this because I get random parts of kernel memory interspersed with >my files (that's the corruption), so I know all of the buffer is not being >filled. You need to queue the rest of the transfer too. I use mine to hold a FFS filesystem too, infact I'm booting from it :) I know I cut off the transfer length, but I also return the missing size in b_resid, so the kernel _should_ come back with the rest of the transfer in a new request or at least fail on the unsatisfied request, and on my system it does seem to work... If this doesn't work in all cases, some other part of the kernel is broken IMHO. I thought of minphys once, but that seems not to work anymore either... -Søren To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
