Well, presuming that these are the source for the firmware in the device, you could probably figure out everything you needed to know.
Of course, that would be like trying to learn to drive by studying how an electronic fuel injection worked. Possible, but not really fun or easy. Here's what you need: The command protocol -- the description of what the host sends to the device to do things. You could reverse-engineer it from the bus traces or the firmware code, but that's painful. How painful? Put it this way: There are people who get paid very good money to do that for a living. In lieu of specs, I'd say that you need to study those bus traces you had before and try to figure those out. Matt On Sun, Feb 09, 2003 at 02:07:54PM -0600, Caylan Van Larson wrote: > Hi eveyone, > > > If it isn't obvious by now, USB is a pretty complex protocol. If you think > > your first driver can work in only 10 hours, when you don't have the specs > > for the device, you are on drugs. > > First of all, thanks Brad for the kick in the ass ;) > > I got these from the manufacturer: > http://www.aero.und.edu/~caylan/mscashdrawer/ > > Would these be considered the "gold" at the end of the rainbow in terms of > specs or just a bunch of crap? -- Matthew Dharm Home: [EMAIL PROTECTED] Maintainer, Linux USB Mass Storage Driver We can customize our colonels. -- Tux User Friendly, 12/1/1998
msg06192/pgp00000.pgp
Description: PGP signature
