Updated: 26 min 47 sec ago
scsi_periph: fixed an "unused" warning.
Time prefs: Use button label symbols & relayout Add becomes +, Remove becomes −, the current button labels "Add" and "Remove" are used as tool tips. Relayout the controls so that they fit nicely with the buttons: The add button is placed left of the server text control showing that it adds new server names while the remove button is placed next to the list view showing that it removes server names from the list. The reset button is placed next to the "Synchronize" button at the bottom of the tab group and is renamed "Reset to default server list". This makes the window a bit taller.
Time prefs: Set text colors in constructor
Time prefs: Set pointer NULL, delete in destructor ... avoiding potential memory leak.
FileRequest: identify unknown files. * WebKit testsuite relies on the MIME types being correct, so when the file doesn't have one, try to identify it. * May be useful for other apps using FileRequest, anyway.
HttpRequest: handle 302 and 307 redirects. * Makes jamendo.com player work, as their soundfiles are behind a temporary redirect for load balancing.
ffmpeg: declare support for webm and 3gpp. * Decoding works on the videos I tested with. * Some videos on Youtube use these formats.
XHTML sniffing rule: handle utf-16 documents.
Add a mime type for XHTML and make Web+ the preferred app. * WebPositive testsuite relies on the mimetype to parse xhtml files. * This has a higher priority than HTML, because it is more reliably detectable * Uses the same icon as html and mhtml. Who wants to draw new ones?
scsi_periph: implemented VPD inquiry. * declared block limits and logical block provisioning structs. * based on SPC-4 and SBC-4 standards.
scheduler: Fix and simplify thread migration logic in low latency mode This patch remove the old thread migration logic which used few special cases and (broken) general check that attempted to balance threads. The new logic is pretty straightforward and seems perform well without any additional special cases. Current core is compared with the least loaded one and the thread is migrated if that would result in estimated loads of both cores (i.e. the current one and the least loaded one) to become closer to the average load (i.e. average of that two cores).
scheduler: Let ThreadData::ShouldRebalance() choose the actual core Currently, ThreadData::ShouldRebalance() (and mode specific functions it calls) only decides whether to migrate thread to another core or not. However, in most cases it actually needs to find the best candidate for new core so it could as well return that information.