On Sun, Jul 05, 2009 at 07:34:10PM +0200, Thomas Martitz wrote:
> By passing something to configure or make, or my manually editing which
> is ok for a release IMO.
I've done that for now. I do think we need a better way in the future
though. It's easy to miss something this way.
Frank
--
"De
On Sun, Jul 05, 2009 at 07:31:49PM +0100, Barry Wardell wrote:
> Since the PP bootloaders are almost all the same, I think it would make
> sense to give all versions released at the same time the same version
> number. So, I suggest we adopt the Sansa numbering for H10 and mr100 too.
I've done th
Jonathan Gordon schrieb:
The other possible option is having a bootloader-version.h in the
bootloader/ folder which is filed with #ifdef #define VERSION
blaaa blocks
Good idea. Maybe only include it if RELEASE or so is defined. It can
then override the VERSION version.sh gave.
On Sun, Jul 5, 2009 at 5:30 PM, Frank Gevaerts wrote:
> In order to release new bootloaders, we need to decide how to solve
> this, and we need to decide on H10 and mr100 bootloader versions.
> Any opinions?
Since the PP bootloaders are almost all the same, I think it would make
sense to give
On Sun, 5 Jul 2009, Bertrik Sikken wrote:
... we have sound on the Meizu M3!
Very cool work Bertrik!
--
/ daniel.haxx.se
Congratulations!
Frank Gevaerts schrieb:
Override it with what? bootloader.make is used for all bootloaders, with
different versions.
Frank
By passing something to configure or make, or my manually editing which
is ok for a release IMO. If we tag a release of some bootloader, this
tag is clearly not mea
2009/7/5 Frank Gevaerts :
> On Sun, Jul 05, 2009 at 07:18:38PM +0200, Thomas Martitz wrote:
>> Jonas Häggqvist schrieb:
>>> Frank Gevaerts wrote:
>>>
>>>
Another way to do this would be to remove APPSVERSION from the
bootloader makefile and set it in config-* instead.
>>>
>>> This se
On Sun, Jul 05, 2009 at 07:18:38PM +0200, Thomas Martitz wrote:
> Jonas Häggqvist schrieb:
>> Frank Gevaerts wrote:
>>
>>
>>> Another way to do this would be to remove APPSVERSION from the
>>> bootloader makefile and set it in config-* instead.
>>>
>>
>> This seems most clear to me, at firs
Jonas Häggqvist schrieb:
Frank Gevaerts wrote:
Another way to do this would be to remove APPSVERSION from the
bootloader makefile and set it in config-* instead.
This seems most clear to me, at first glance - in combination with a flag
in show_logo.c whether to use BOOTLOADER_VERSION
I spent the last week up to my elbows in buffering.c. It's not quite
ready yet, but it's looking good; the patch is at
http://q3q.us/buffer2.patch . Here's what's going on:
- I decided the reservation of independent buffer space was just too
cruel to live and scratched it.
- The code here inst
Frank Gevaerts wrote:
> Another way to do this would be to remove APPSVERSION from the
> bootloader makefile and set it in config-* instead.
This seems most clear to me, at first glance - in combination with a flag
in show_logo.c whether to use BOOTLOADER_VERSION (or whatever is decided
to call i
Portalplayer bootloader versions are a bit confusing:
Sansa bootloaders have nice version numbers. The current version is 5.0,
the next will be 6.0
Released H10 and mr100 bootloaders don't have version numbers, and use svn
revisions instead. H10 is r12862:12866-070320, mr100 is r12345-080318.
Th
On Sun, Jul 05, 2009 at 04:55:57AM +0200, Thomas Martitz wrote:
> I've just created a branch at
> http://svn.rockbox.org/viewvc.cgi/branches/bootloader_ams_pp/
If you also want to check out this branch, the svn url is:
svn://svn.rockbox.org/rockbox/branches/bootloader_ams_pp
Frank
--
"Debugg
... we have sound on the Meizu M3!
The sound was the first two seconds of "On my way" by Giovanca, as a raw
wav statically compiled in the Meizu bootloader (we can't run a "normal
rockbox" yet on the Meizus).
So, it's not a full song yet, but it does prove that the audio codec
communication, PCM
On Sun, Jul 5, 2009 at 10:07 AM, Hussein Patwa wrote:
> I haven't used this myself as I'm only just getting into it, but is the
> simulator not an option or does that not help with testing boot loaders?
You can't test the bootloaders in the simulator. The simulators
purpose is mainly to simulate t
in the simulator. The simulators
> purpose is mainly to simulate the UI, thus it doesn't emulate any
> hardware. The bootloader, however, needs to run on the physical
> hardware.
Thanks. I learn something new every day.
__ Information from ESET Smart Security, version o
> I think I know what to do to fix FS#9642 (Bootloader USB Diskmode
> fails to exit gracefully on CFModded H100) -- a simple addition of one
> line of code. I've posted the diff in the comments for the bug. I
> don't know how to test it, though, without risking bricking my player.
> What can I
I think I know what to do to fix FS#9642 (Bootloader USB Diskmode
fails to exit gracefully on CFModded H100) -- a simple addition of one
line of code. I've posted the diff in the comments for the bug. I
don't know how to test it, though, without risking bricking my player.
What can I do to avoid
19 matches
Mail list logo
