Rockbox

Tasklist

FS#7588 - ata_wakeup()

Attached to Project: Rockbox
Opened by Timo Horstschäfer (x1jmp) - Sunday, 12 August 2007, 18:41 GMT
Last edited by Frank Gevaerts (fg) - Saturday, 04 June 2011, 21:44 GMT
Task Type Patches
Category Drivers
Status Closed
Assigned To No-one
Operating System All players
Severity Low
Priority Normal
Reported Version Daily build (which?)
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

The ata_wakeup() function does the opposite of ata_sleep(), it spins up the hard-disk in background.
This makes it possible to start the disk in advance to reduce access time later.

It also eliminates some duplicate code lines in ata.c.
This task depends upon

Closed by  Frank Gevaerts (fg)
Saturday, 04 June 2011, 21:44 GMT
Reason for closing:  Out of Date
Comment by Nicolas Pennequin (nicolas_p) - Sunday, 12 August 2007, 18:54 GMT
I like the idea, especially as I thought this existed already and I'm going to need it soon :)

One remark, though: don't add functions to the plugin API in the middle of the struct, it breaks binary compatibility. You should add them at the end. FYI, when the struct is reordered, the plugin API version needs to be bumped.
Comment by Jonathan Gordon (jdgordon) - Sunday, 12 August 2007, 21:58 GMT
this will break the ondio and sansas... you need to add a ata_wakeup() stub in firmware/drivers/ata-mmc.c and firmware/target/arm/sandisk/sansa-e200/ata-e200.c
Comment by Timo Horstschäfer (x1jmp) - Sunday, 12 August 2007, 23:08 GMT
Stubs added and moved ata_wakeup() to the end of the plugin API.
Comment by Rosso Maltese (asettico) - Sunday, 02 March 2008, 11:56 GMT
The patch doesn't apply with build 2008-03-01 (r16460).
Is it possible to sync it?
TYA
Comment by Jonathan Gordon (jdgordon) - Sunday, 02 March 2008, 12:22 GMT
Rosso: DO NOT ASK FOR RESYNCS
Comment by Rosso Maltese (asettico) - Sunday, 02 March 2008, 12:36 GMT
Why I have not to do it? Is there something like an etiquette I didn't read?
If the patch is no more useful because it was included in the main trunk or it became "obsolete", should it mark as closed?
Thanks for the attention.
Comment by Jonathan Gordon (jdgordon) - Sunday, 02 March 2008, 13:10 GMT
it annoys developers. i the patch was commited then yes this would be closed, but it isnt so it isnt
Comment by Hideyuki Kanaya (Lucid) - Wednesday, 16 July 2008, 07:27 GMT
resync

I hope this works...

Loading...