Re: PATCH: cdrecord: avoiding scsi device numbering for ide devices

From: Gene Heskett
Date: Tue Aug 10 2004 - 22:14:08 EST


On Tuesday 10 August 2004 20:24, Matthias Andree wrote:
>On Tue, 10 Aug 2004, Gene Heskett wrote:
>
>[burnproof decreases CD quality]
>
>> How so Joerg? Making a blanket statement such as this requires a
>> good proof example IMO. You not are giving one.
>
>The switch from read mode to write mode (i. e. find end of data,
>increase LASER power to write and pick up writing) takes some time
>(order of magnitude: µs) which means some pits/lands aren't right
> during that phase. How many pits/lands are broken break depends on
> hard- and firmware, write speed and model and for CAV the radial
> position on the disc. Fast writers will need to reach a linear
> velocity around 60 m/s (216 km/h); one µs time to ramp up LASER
> power from read to write level there means up to 60 µm lost.

And just how fast do you think that laser is being modulated? At the
bandwidth of that, the lazer's power could be brought back to write
power levels in at least an order of magnitude less time than that.

I'd be far more concerned with the support electronics ability to
detect the end of the previous write in a timely manner than in how
long it took to bring the laser back up to write power. My guess is
that any space lost, and therefore unwritten on the disk, is much
more an issue of detecting the loss than in 'ramping up the power'
which can be done in modern drives in 5ns or less. Now if the
electronics could detect the first missing edge and initiate the
write on that, the written edge needn't be more than 5ns late, a very
minor glitch in the data recovery's phase locked loop, and probably
fully recentered before the next 100 edges have gone by, certainly
before the intersector synch data is used up and real data begins.

But, now consider this, a drive with burnproof should have a method of
marking a burnproof event in the intersector sync data. The drive
should have at the point when the burnproof kicked in, written a
known bit pattern that identifies a burnproof event in the
intersector housekeeping. From that, the drive can predict the end
of the written data to a very high degree of accuracy, and switch up
the laser precisely on time to not miss a pits edge at all.

So I don't find this argument convincing unless the drive makers are a
bunch of dummies and haven't thought of the above scenario. That
theory doesn't hold any water either. The designers of these things
will use every possible advantage to make their product a better
mousetrap. You can bet the farm that this method, or one even better
is in use in every drive featureing burnproof today.

Much of what I just wrote could, I suppose, be considered proprietary
data to the drive makers, and if I 'blew their cover', well stuff
happens... You cannot argue with common sense solutions to what
looks like a complex problem to the average Joe Six-Pack.

And there's precious few of us here who think we're the Joe Six-Packs
of this world. "They" are not those who would subscribe to this list
in the first place. Generally speaking, we like to think we're a cut
above that label... Granted, there are many younger, brighter brains
than mine on this list, and for that I'm thankfull every day.

>How far good improvements in the hard- and firmware have allowed to
>reduce that gap is beyond my current knowledge. Some figures are
> posted at: http://www.digital-sanyo.com/BURN-Proof/tips/No1.html
> http://www.digital-sanyo.com/BURN-Proof/tips/No2.html

Moot point IMO, progress is made everyday by the drive people.
Progress they aren't going to talk about for the competitive edge
they need because if they did, the guy down the street would be out
with a clone later today. So take anything that purports to be "the
bible" with an un-healthy amount of salt.

--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.24% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/