On 19-Dec-2002 Matthew Dillon wrote:
This is a real mess but I finally got it to work. (Note
to John: both quirk entries are absolutely necessary,
everything stalls and dies without them).
You might need to lie to umass and tell if to use the UFI or ATAPI
protocols instead of
On Thu, Dec 19, 2002 at 05:11:32PM -0800, Matthew Dillon wrote:
I found another couple of bugs, this time in OHCI's DMA
buffer chaining code.
Great.
A patch for this with additional debugging code is
included below (for current). There are two bugs.
I do not know if
:The NetBSD code is already different:
:1.48 (augustss 15-Sep-99): /* The OHCI hardware can handle at
:most one page crossing. */
:1.48 (augustss 15-Sep-99): if (OHCI_PAGE(dataphys) ==
:dataphysend ||
:1.48 (augustss 15-Sep-99):
Hey, Matt
While you're at it, could you have a look at PR kern/46176 ? =)
At least would you tell me if you have the same problem with your
device(s)
On Thu, 2002-12-19 at 11:32, Matthew Dillon wrote:
It took a hellofalong time pulling my hair out trying to figure out
why the Sony
On Thu, Dec 19, 2002 at 02:32:23AM -0800, Matthew Dillon wrote:
It took a hellofalong time pulling my hair out trying to figure out
why the Sony disk-on-key I just bought didn't work.
First I added a Quirk entry for the standard 6-byte problem, but it
didn't solve the
On Thu, Dec 19, 2002 at 12:08:27PM +0100, Frode Nordahl wrote:
Hey, Matt
While you're at it, could you have a look at PR kern/46176 ? =)
At least would you tell me if you have the same problem with your
device(s)
The umass cam interaction is questionable.
I've seen lots of problems caused
:
:On Thu, Dec 19, 2002 at 12:08:27PM +0100, Frode Nordahl wrote:
: Hey, Matt
:
: While you're at it, could you have a look at PR kern/46176 ? =)
:
: At least would you tell me if you have the same problem with your
: device(s)
:
:The umass cam interaction is questionable.
:I've seen lots of
:
: Note that my other UMASS device, a compact flash reader, has always
: worked fine with just the Quirk entry. I really need a USB expert to
: tell me what is going on :-)
:
:The problem is that an umass bulk only umass device is allowed to stall the
:comunication pipe on an
On 19-Dec-2002 Matthew Dillon wrote:
It took a hellofalong time pulling my hair out trying to figure out
why the Sony disk-on-key I just bought didn't work.
First I added a Quirk entry for the standard 6-byte problem, but it
didn't solve the problem.
You don't need the
On Thu, Dec 19, 2002 at 09:06:19AM -0800, Matthew Dillon wrote:
:
:On Thu, Dec 19, 2002 at 12:08:27PM +0100, Frode Nordahl wrote:
: Hey, Matt
:
: While you're at it, could you have a look at PR kern/46176 ? =)
:
: At least would you tell me if you have the same problem with your
:
On Thu, Dec 19, 2002 at 12:24:09PM -0500, John Baldwin wrote:
On 19-Dec-2002 Matthew Dillon wrote:
It took a hellofalong time pulling my hair out trying to figure out
why the Sony disk-on-key I just bought didn't work.
First I added a Quirk entry for the standard 6-byte
: didn't solve the problem.
:
: You don't need the 6-byte quirk entries anymore. The umass(4) driver
: automatically handles 6-byte commands (converting them to 10-byte commands)
: and has done so for a while now. You should at least try removing the
: 6 byte quirk for now.
:
:I tought
On 19-Dec-2002 Bernd Walter wrote:
On Thu, Dec 19, 2002 at 12:24:09PM -0500, John Baldwin wrote:
On 19-Dec-2002 Matthew Dillon wrote:
It took a hellofalong time pulling my hair out trying to figure out
why the Sony disk-on-key I just bought didn't work.
First I added a
On Thu, Dec 19, 2002 at 12:49:16PM -0500, John Baldwin wrote:
On 19-Dec-2002 Bernd Walter wrote:
On Thu, Dec 19, 2002 at 12:24:09PM -0500, John Baldwin wrote:
On 19-Dec-2002 Matthew Dillon wrote:
It took a hellofalong time pulling my hair out trying to figure out
why the Sony
:
: Eh? For ATAPI and UFM devices we never send a 6 byte command to the
: device that can fail, only 10 byte commands.
:
:I believed this was a SCSI over bulk only device.
:
:--
:B.Walter COSMO-Project http://www.cosmo-project.de
:[EMAIL PROTECTED] Usergroup
This is a real mess but I finally got it to work. (Note
to John: both quirk entries are absolutely necessary,
everything stalls and dies without them).
Problem #1: RA_NO_CLEAR_UA quirk required in umass.c.
Problem #2: RA_NO_CLEAR_UA quirk code is broken,
On Thu, 19 Dec 2002, Bernd Walter wrote:
On Thu, Dec 19, 2002 at 09:06:19AM -0800, Matthew Dillon wrote:
The panic described in 46176 has happened to me on -current. On
-stable I have managed (very easily) to get the CAM layer vs UMASS
layer into a confused state where the CAM
On Thu, Dec 19, 2002 at 03:24:28PM -0800, Nate Lawson wrote:
On Thu, 19 Dec 2002, Bernd Walter wrote:
On Thu, Dec 19, 2002 at 09:06:19AM -0800, Matthew Dillon wrote:
The panic described in 46176 has happened to me on -current. On
-stable I have managed (very easily) to get the
On Thu, 19 Dec 2002, Matthew Dillon wrote:
Yes, this is a USB DiskKey - UMASS storage, SCSI over bulk only device.
I've done some further testing on both -current and -stable. I cannot
get the device to work unless I have the quirk entry in scsi_da.c.
-Current has a quirk
On Thu, Dec 19, 2002 at 04:25:40PM -0800, Nate Lawson wrote:
if (csio-ccb_h.flags CAM_CDB_POINTER) {
cmd = (unsigned char *) csio-cdb_io.cdb_ptr;
} else {
cmd = (unsigned char *) csio-cdb_io.cdb_bytes;
:
: -Current has a quirk table for umass.c and already has a flag which
: disables the residue test. The patch for current thus does not require
: #if 0'ing out that code, only a quirk entry. Since I don't need any
: hacks beyond what is there already I am going to commit the
:First, the calculation of dataphysend is totally bogus.
:You can just take the physical address and add (len - 1)
:to it. You have to take the virtual address, add len - 1
:to it, and convert it to a physical address. I can
:crash my machine simply by doing a
God, my
22 matches
Mail list logo
