Robin Paulson wrote: > 2008/11/2 Dale Maggee <[EMAIL PROTECTED]>: >> It's not impossible because of the pause while downloading, I'd just >> make NeoTool download the file before showing the "About to flash, >> Please boot to the menu" message. > > ok, that should work > >> One problem I had was determining where to get the files, and how to >> tell when there's a new release - I'd rather not hard code addresses >> into it, so for this to work there would need to be something like: >> >> http://downloads.openmoko.com/releases/latest/release.jffs2 >> http://downloads.openmoko.com/releases/latest/kernel.bin >> >> you say "there is a link on the om site pointing to the 'latest' >> kernel/uboot/rootfs to download"... which link are you referring to?
One should also consider offering FDOM and QtExtended, not only the OM release. > > http://downloads.openmoko.org/releases/Om2008.9/Om2008.9.rootfs.jffs2 > which has the same date stamp and size as the newest file > > and so on > >> Another issue I had was determining which files to download: I'd need to >> prompt to find out whether to get the GTA01 or GTA02 files. > > i'm sure this can be found from the command-line, and hence a bash > script by ssh'ing into the phone before re-booting. or use a button to > do it manually, if the user doesn't want to do that > > >> Alternatively, I guess it would be possible to traverse >> downloads.openmoko.org and present a menu allowing the user to specify >> what to download, but I don't know how to at the moment, and this is >> basically duplicating the functionality of pointing your browser to this >> address, so it seems kind of redundant to me. > > still a bit clumsy - humans are so good at making mistakes; i'm > paranoid about flashing the wrong thing and screwing my phone. > > at worst, you could parse the contents of the html, find the latest > release by some text manipulation and go from there. assuming om don't > change the layout and structure > but yes, this is probably no small work, and as you say, is > duplicating the browser > >> In the end I decided not to do it because I figured I'd basically be >> duplicating your browser's functionality, and that I would be better off >> devoting my efforts to more Neo-specific stuff, like adding the ability >> to backup. > > sure. each has their own ideas. maybe i'm going over the top, and it's > simple enough already? > > _______________________________________________ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community