From: <sc...@hu...> - 2007-07-08 16:42:42
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The current cdrdao tarball's version of scsilib is too low to compile properly on the intel-based Macs. We need Schily's a27 version at the very least, where he introduced support for i386-darwin. After figuring out how cdrdao does its magic under its scsilib tree, I first made sure a27 would work before upgrading to a29, as a29 is suppose to have bluray support now and has some massive changes (so the ANnouncement files on a28 & a29 say). Yes I am actually able to kludge cdrdao-1.2.2 to compile & link with the a29 the same way. Here's some bit of proof it's working on my new 24-inch iMac Core2 Duo stock machine: $ cdrdao drive-info Cdrdao version 1.2.2 - (C) Andreas Mueller <an...@da...> SCSI interface library - (C) Joerg Schilling Paranoia DAE library - (C) Monty Check http://cdrdao.sourceforge.net/drives.html#dt for current driver tables. Using libscg version 'schily-0.9' IODVDServices: MATSHITA DVD-R UJ-85J Rev: FCQA Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000) Maximum reading speed: 4234 kB/s Current reading speed: 4234 kB/s Maximum writing speed: 4234 kB/s Current writing speed: 4234 kB/s BurnProof supported: yes JustLink supported: yes JustSpeed supported: no $ cat /etc/cdrdao.conf write_device:"IODVDServices" cddb_server_list:"freedb.freedb.org:/~cddb/cddb.cgi" $ $ file /usr/local/bin/cdrdao /usr/local/bin/cdrdao: Mach-O executable i386 i.e. at least cdrdao+cdrtools can see the drive and it's native i386 code. (I need to upgrade 'file' so it can report .a files properly; for now you'll just have to trust me the .a's are i386-native, too ;) .) How 'bout that? :) btw I can't possibly test bluray support unless/until someone might want to donate a firewire enclosure with one of them expensive critters in it. ;) Supposedly Toast 8.0.1 has a kext that we can use for comparisons. I will attempt to try those native SCSI patches from Edgar Fuß <ef...@ma...> next. But I think I need to take a nap first. ;) Stay tuned. -----BEGIN PGP SIGNATURE----- Note: This signature can be verified at https://www.hushtools.com/verify Version: Hush 2.5 wkYEARECAAYFAkaRE50ACgkQZbt5KOxKrtR8bwCgqBInPSw5U7wOHR5KoanxyhDuxmMA nj9/yKQKJfMJNVZkHV9mNqm3ZEAt =R0KG -----END PGP SIGNATURE----- |