Date: Thu, 9 Jan 1997 20:22:02 -0800 (PST) From: John-Mark Gurney <jmg@nike.efn.org> To: Frank Durda IV <uhclem@nemesis.lonestar.org> Cc: freebsd-bugs@freebsd.org, joerg_wunsch@uriah.heep.sax.de Subject: Re: bin/2303 & kern/2423 CDs and BCD numbers - its 99 DECIMAL not HEX Message-ID: <Pine.NEB.3.95.970109201217.12973R-100000@hydrogen.nike.efn.org> In-Reply-To: <m0viY1P-000us7C@nemesis.lonestar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 9 Jan 1997, Frank Durda IV wrote: [...] > Now, there are plenty of makes of CD-ROM drives that return info to > the host in BCD, and this is because most of the fields on the actual disk > are in BCD. This means less work for the drive. The Matsushita proprietary > interface drives are good examples of drives that do this. > > However, BCD or not, any disc with more than 99 DECIMAL tracks is > encoded incorrectly, will malfunction in many different drives, > and technically the company that pressed the disc is in violation of > their CD manufacturing license to Philips. (Supposedly there is a > reward for reporting license violators...) [...] actually... as it turns out I'm pretty sure that this drive returns all track id's as bcd... so I have pattched the kernel to add a specific option to enable bcd->binary conversion and back for broken drives... you have to add an entry to the quirks list for the drives that need bcd conversion... so it won't affect the rest of the `normal' cdroms... if you would like to look at the patches check out kern/2423... I've also done a follow up at bin/2303 that states that when kern/2423 is committed than bin/2303 should be closed as kern/2423 fixes it... and thanks for the info... ttyl... John-Mark gurney_j@efn.org http://resnet.uoregon.edu/~gurney_j/ Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.95.970109201217.12973R-100000>