Bug 11881 – TinySC needs to send correct SqueezePlay f/w update URLs

Bug 11881 - TinySC needs to send correct SqueezePlay f/w update URLs

Summary:

TinySC needs to send correct SqueezePlay f/w update URLs

Status:	CLOSED FIXED

Product:	SB Touch
Classification:	Unclassified
Component:	TinySC
Version:	unspecified
Platform:	PC Windows XP

Importance:	P1 major (vote)
Target Milestone:	7.5.0
Assigned To:	Michael Herger

URL:
Keywords:	TinySC

Depends on:	10455
Blocks:
	Show dependency tree / graph

Reported:	2009-04-22 00:54 UTC by Alan Young
Modified:	2010-04-08 17:26 UTC (History)
CC List:	4 users (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Alan Young 2009-04-22 00:54:53 UTC

... for Fab4 and/or Jive?

Comment 1 Spies Steven 2009-04-22 09:22:10 UTC

I believe bug 9149 somewhat is related.  Not sure what the status of that bug is though.

Comment 2 Blackketter Dean 2009-04-22 16:57:27 UTC

I don't see why it would behave differently than SC in this regard.

Comment 3 Alan Young 2009-09-29 02:01:37 UTC

I think that we just need to ensure that the updatesdir will be on flash, not external storage. SC already now only downloads all f/w updates as necessary for connected devices.

Comment 4 Seth Schulte 2009-10-08 10:26:30 UTC

We should not support local download of firmware updates for TinySC. We should give SP the URL from SN.

Comment 5 SVN Bot 2009-11-26 09:27:44 UTC

 == Auto-comment from SVN commit #29486 to the slim repo by michael ==
 == https://svn.slimdevices.com/slim?view=revision&revision=29486 ==

Fixed Bug: 11881
Description: enable direct firmware download to players, without caching updates on the server

new Slim::Utils::OS::directFirmwareDownload property allows 3rd parties to do the same

don't load server update code on SqueezeOS - it's being updated through the firmware updates

Comment 6 Chris Owens 2010-04-08 17:26:26 UTC

This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release.

If you are still seeing this issue, please let us know!