Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'A patch for the Prolific USB serial driver' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A patch for the Prolific USB serial driver
Authored by: LC on Sep 25, '03 07:40:37PM
In step 4, to avoid having to do hand edits, I suggest this instead --

hexdump -s 0x2288 -n 4 ProlificUsbSerial
(* it should output "4800 0008" at 0002288 *)

printf "\070\140\000\000" | dd bs=4 seek=2210 count=1 conv=notrunc of=ProlificUsbSerial

hexdump -s 0x2288 -n 4 ProlificUsbSerial
(* it should now output "3860 0000" at 0002288 *)

dd is /bin/dd, the other two (printf and hexdump) are from /usr/bin
All I did is to make the edit non-interactive, so you can copy/paste the command or script it. Larry.

[ Reply to This | # ]

A patch for the Prolific USB serial driver
Authored by: LC on Sep 25, '03 07:45:35PM
Sorry, my backslashes got eaten (in the printf command), let's try this instead --
printf "\070\140\000\000" | dd bs=4 seek=2210 count=1 conv=notrunc of=ProlificUsbSerial
Sorry, it looked o.k. when I previewed it, I thought;
there needs to be one backslash leading each of the 4 octal codes.

[ Reply to This | # ]
A patch for the Prolific USB serial driver
Authored by: Bobson on Sep 26, '03 12:26:34AM

I've encountered the same thing. A double backslash in code in the preview becomes a single backslash when posted....



[ Reply to This | # ]
A patch for the Prolific USB serial driver
Authored by: LC on Sep 26, '03 11:18:53AM

Thanks; I felt a bit foolish after that happened yesterday, but I
haven't posted much using geeklog so I didn't know that the
preview isn't final in the case of backslashes. I still don't
understand how many times they need to call stripslashes, i.e.
could they do it all prior to preview ... that should be a FAQ; Larry.



[ Reply to This | # ]