dev builds
themes manual
device status forums
mailing lists
IRC bugs
dev guide

Rockbox mail archive

Subject: Re: Feature freeze - silent play (wasRe: #673350 'Improvements for status line')

Re: Feature freeze - silent play (wasRe: #673350 'Improvements for status line')

From: Björn Stenberg <>
Date: Fri, 11 Apr 2003 23:11:57 +0200

Mike Holden wrote:
> My remaining issue is "Silent Play".

I believe silent play is an mpeg issue (misinterpreting vbr headers etc) and not a disk reading issue. I also haven't seen any reports about this since Linus fixed some problems in the mpeg code a while ago. Feel free to brief us if this happens to you.

> The code comment has 5 * nop, and the comments says 400ms. Where did this
> figure come from? Is it the ATA spec? How long does a nop take,

Yes, the 400ns is defined in the PIO protocol part of the ATA specification:

"HPIOI1: Check_Status State:
This state is entered when the host has written a PIO data-in command to the device and nIEN is set to one, or when INTRQ is asserted.
When in this state, the host shall read the device Status register. When entering this state from the HI4 state, the host shall wait 400 ns before reading the Status register."

A nop instruction takes one clock cycle, and since the cpu is clocked at 12 MHz each cycle is 83ns long.

Received on 2003-04-11

Page template was last modified "Tue Sep 7 00:00:02 2021" The Rockbox Crew -- Privacy Policy