optcd 2.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657
  1. This is the README file for the Optics Storage 8000 AT CDROM device driver.
  2. This is the driver for the so-called 'DOLPHIN' drive, with the 34-pin
  3. Sony-compatible interface. For the IDE-compatible Optics Storage 8001
  4. drive, you will want the ATAPI CDROM driver. The driver also seems to
  5. work with the Lasermate CR328A. If you have a drive that works with
  6. this driver, and that doesn't report itself as DOLPHIN, please drop me
  7. a mail.
  8. The support for multisession CDs is in ALPHA stage. If you use it,
  9. please mail me your experiences. Multisession support can be disabled
  10. at compile time.
  11. You can find some older versions of the driver at
  12. dutette.et.tudelft.nl:/pub/linux/
  13. and at Eberhard's mirror
  14. ftp.gwdg.de:/pub/linux/cdrom/drivers/optics/
  15. Before you can use the driver, you have to create the device file once:
  16. # mknod /dev/optcd0 b 17 0
  17. To specify the base address if the driver is "compiled-in" to your kernel,
  18. you can use the kernel command line item (LILO option)
  19. optcd=0x340
  20. with the right address.
  21. If you have compiled optcd as a module, you can load it with
  22. # insmod /usr/src/linux/modules/optcd.o
  23. or
  24. # insmod /usr/src/linux/modules/optcd.o optcd=0x340
  25. with the matching address value of your interface card.
  26. The driver employs a number of buffers to do read-ahead and block size
  27. conversion. The number of buffers is configurable in optcd.h, and has
  28. influence on the driver performance. For my machine (a P75), 6 buffers
  29. seems optimal, as can be seen from this table:
  30. #bufs kb/s %cpu
  31. 1 97 0.1
  32. 2 191 0.3
  33. 3 188 0.2
  34. 4 246 0.3
  35. 5 189 19
  36. 6 280 0.4
  37. 7 281 7.0
  38. 8 246 2.8
  39. 16 281 3.4
  40. If you get a throughput significantly below 300 kb/s, try tweaking
  41. N_BUFS, and don't forget to mail me your results!
  42. I'd appreciate success/failure reports. If you find a bug, try
  43. recompiling the driver with some strategically chosen debug options
  44. (these can be found in optcd.h) and include the messages generated in
  45. your bug report. Good luck.
  46. Leo Spiekman (spiekman@dutette.et.tudelft.nl)