On 16/07/11 15:38, Jonathan Gordon wrote:
On 14 July 2011 05:36, Sean Bartellwingedtachik...@gmail.com wrote:
One issue raised about these changes is where the librbcodec files
should be moved. My current version moves them to /rbcodec, with dsp,
metadata, and codecs subdirectories. Saratoga
Sean Bartell wrote:
On Sun, May 15, 2011 at 09:22:07PM +0200, Al Le wrote:
The initial focus will be on getting the library working, not on a nice
API. In order to appeal to software other than Rockbox...
IMO the API should be laid out first. How else can you say that the
library works?
Hi,
The Release 3.7, freeze on Monday thread seems to have been hijacked,
so to bring the subject up again, are we freezing now?
I'm also trying to catch up on Rockbox developments over the past few
months, and am wondering if the theme breakage is a reason to bump to 4.0?
I've read the
Jonathan Gordon wrote:
I have a few problems with this idea.
First, what is the bar to decide if we actually need to vote before a
commit? everything? everything not trivial?
If we're talking new features, then it could simply be anything that
changes behaviour of Rockbox for users - i.e.
Jonathan Gordon wrote:
Lastly I'll remind the people that need reminding that everyone here
is doing it as a hobby, when it doesnt become fun anymore people
leave. The only people who could be considered having any authority to
activly force someone to work on something (or not work on
Jonathan Gordon wrote:
On 9 October 2010 22:32, Dave Chapman d...@dchapman.com wrote:
But my personal view is that features should only be added to Rockbox when
there is a general concensus that it is a good idea. When 95% of devs don't
express an opinion on a new feature, then I would read
Thomas Martitz wrote:
I think most of us (including me) prefer andriod. I personally
*strongly* prefer it since I had an HTC legend in my hands :) Is anyone
uncomfortable with that?
It's your project, so ultimately I think the choice is yours - you
should port RaaA to whatever interests you.
pouly amaury wrote:
What do you think about it? Do you have any ideas how my proposal
could be improved? Or do you have any questions? Please join the
discussion.
Sounds ok for me, I like the idea of the simulator being a real target.
Apologies for answering so late (too late in
Thomas Martitz wrote:
My understanding of the purpose of RaaA is that it would use less and
less of the Rockbox firmware code as time went on. Development of the
sim should go in the opposite direction - using more and more Rockbox
code.
No, I don't think RaaA aims to use less and less
Frank Gevaerts wrote:
On Sun, May 16, 2010 at 02:23:36PM +0100, Dave Chapman wrote:
I don't really think the simulator can use much more core rockbox code
without becoming an emulator.
I'm not saying that the uisim can use more Rockbox code, just that RaaA
should use less, and that over
Paul Louden wrote:
So I'm wondering if one easy (and free!) thing someone could do is to
collect this information together in some kind of Future targets
wiki page, to try and promote these as tasks people could work on.
We should probably set some minimum requirement for the future target
Paul Louden wrote:
On 3/23/2010 3:13 PM, Mike Giacomelli wrote:
Anyway, without a rational the NODO list is kind of bizarre. We
should have a
So how do you give an objective rationale why one feature is worth the
size, and another isn't? Some things will have to be subjective, it's
just a
asettico wrote:
I discover two statements ifdef-ed out in bootloader/ipod.c:313 since
r7784 (the first revision of this file).
Do you see any problem to enable those lines or something could get
break? (Unfortunately I have no knowledge about the RB architecture and
I can't build a FW now).
Rafaël Carré wrote:
On Thu, 29 Oct 2009 23:46:50 +0100
Alex Parker parker.ale...@gmail.com wrote:
Hi All,
I'd like to have the beast as unstable - it has a released bootloader
and released beastpatcher versions for linux (32 and 64 bit) and
windows, and the manual contains manual install
Alex Parker wrote:
Hi All,
I'd like to have the beast as unstable - it has a released bootloader
and released beastpatcher versions for linux (32 and 64 bit) and
windows, and the manual contains manual install instructions. Only mac
is missing, owing to a lack of developers on that platform.
All,
I've been thinking a bit about the target classifications, and have come
to the conclusion that we now have a large number of ports, in a wide
variety of states of completion, that the current 3 categories is not
enough.
I would like to see the addition of a top-tier category - one
Thomas Martitz wrote:
I've just created a branch at
http://svn.rockbox.org/viewvc.cgi/branches/bootloader_ams_pp/
Use this branch to commit version number changes or whatever needed to
get nice bootloaders out for affected targets. Also use this for the
installers (mkamsboot, sansapatcher,
Frank Gevaerts wrote:
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,
Thomas Martitz wrote:
Late reply. I don't see any problem with the branch anyway.
Any time would have been too late, as you had already created the
branch... Just because you don't see a problem with the branch, doesn't
mean no-one else does/will.
Anyway, I didn't know the usual way of
Jonathan Gordon wrote:
OK, nice patch... still not as clean as mine (I'm entitled to my
opinion..) but if thats what it takes to be accepted so be it. I'll
test it out tonight
What about the subject of this thread? Will you be reverting r21307?
Regards,
Dave.
mai...@svn.rockbox.org wrote:
Date: 2009-06-16 07:14:51 +0200 (Tue, 16 Jun 2009)
New Revision: 21307
Log Message:
For those who dont have the memory of a Something that has really
good memory show in the main menu that there is nothing to resume to
stop the annoying nothing to resume splash
Rafaël Carré wrote:
The problem is htole16 and htole32 are defined in endian.h (under ifdef
__USE_BSD)
I believe this is a bug in Ubuntu, but if other OS (BSD?) provide these
functions they should be under #ifndef htole16 ?
I don't think this is a Ubuntu problem - those macros were added with
Jonas Häggqvist wrote:
A while ago, it was decided that themes on the fabled theme site should be
required to be licensed exclusively CC-BY-SA. This however, results in
some problems. For one thing, we can't reuse parts of themes in the
Rockbox defaults since they're part of the code, and hence
Jonathan Gordon wrote:
I'm sure I've said it before, and I doubt I'm alone... there is a
difference between customizable buttons (which everyone agrees will be
a support nightmare) and allowing the user to choose between a few
select options for individual buttons when there is a free button to
Alex Bennee wrote:
Hi,
I've noticed that sometimes when Rockbox shuts down it leave the boot
code confused as to the charge state of the battery. The iPod will
refuse to boot with the usual Menu key and when plugged in to the USB
reports very low battery. Once I give it the two finger salute
mai...@svn.rockbox.org wrote:
Date: 2009-02-19 23:15:02 +0100 (Thu, 19 Feb 2009)
New Revision: 20055
Log Message:
Add generic touchscreen driver which allows calibration (apps/ layer will
follow later).
[snip]
Added: trunk/firmware/drivers/touchscreen.c
[snip]
+/* Based on
mai...@svn.rockbox.org wrote:
Date: 2009-01-23 19:34:06 +0100 (Fri, 23 Jan 2009)
New Revision: 19826
Log Message:
Fix wpsbuild.pl not installing all required fonts
Even though it turns out that it was due to a bug, I had always thought
that the behaviour of only including the font required
Rafaël Carré wrote:
If sendfirm_win.c is redistributed with the LGPL, it can be linked with
any proprietary library, no ?
Yes, I think so. Or maybe BSD. Although we can only do that if we know
the license from the code taken from creative.com, and it still means
that we can't incorporate
All,
This has been discussed a few times in IRC over the past couple of days,
but I thought it would be useful to bring it here - especially as the
two people responsible for that code (mcuelenaere and nicolasp) haven't
been involved in those discussions.
For those that may not know,
mai...@svn.rockbox.org wrote:
Date: 2009-01-05 00:46:44 +0100 (Mon, 05 Jan 2009)
New Revision: 19675
Log Message:
The Gigabeat S is considered supported as of now
How is it supported? There is no manual, no Windows installation
instructions, no dual-boot install instructions, no
Björn Stenberg wrote:
Paul Louden wrote:
my battery percentage will appear to be down a percent or two just
from browsing the menus.
I we need hard data before playing the think of the runtime card.
I think a user can still scroll down.
Of course he can. So why do we not choose 3 seconds
Jonathan Gordon wrote:
I'm not against the idea, but I wonder what the point of releasing so
often is unless there was something big?
The point is to keep the most recent stable release recent. We want
users to (in general) use the releases, and if we stick to a relatively
short (and fixed)
[EMAIL PROTECTED] wrote:
Date: 2008-10-19 05:58:33 +0200 (Sun, 19 Oct 2008)
New Revision: 18832
Log Message:
Dont show lines which have no info in the id3 viewer screen.
Modified:
trunk/apps/screens.c
Why was this feature change committed without any pre-commit discussion
at all? It
Rafaël Carré wrote:
On Sun, Oct 19, 2008, [EMAIL PROTECTED] wrote:
Date: 2008-10-19 16:11:01 +0200 (Sun, 19 Oct 2008)
New Revision: 18836
Log Message:
Add e200v2 and m200v2 targets. Move the telechips lcd-ssd1815.c (currently
used by Logik DAX and m200v1 ports) driver up in the target tree
Daniel Dalton wrote:
I was just trying to look for a solution to accessibility, since it
doesn't seem to be a priority.
Given the current level of accessibility Rockbox provides, how can you
say that the Rockbox developers don't give it a priority.
Of course it can be improved (as can all
Daniel Dalton wrote:
What about maintaining this compilation of patches on a forum thread or
on a bug tracker entry, instead of the SVN repository ?
We could do that, or perhaps another way would be to put the
accessibility directory in the root eg just above trunk... So then there
is a sub
Marc Guay wrote:
My eyes are drawn straight away to the words playback and radio: these
look out of place here (sloppy, even) without capitalisation. I don't think
Rockbox should differ from the vast majority of English software (UK, US or
otherwise) in this respect.
I think it goes without
Paul Louden wrote:
XavierGr wrote:
I have to agree, sentence case seems the way to go.
Title case is used mostly in English and not other languages.
Well this discussion is mostly about English, since pretty much no other
language uses it regularly anyway and I don't think we'd impose title
I've recently been trying to sync the Catalan translation, and have
noticed the inconsistent use of title and sentence case in the lang files.
A recent(-ish) patch (FS#8538 - committed as r16663) fixed a lot of
inconsistencies by making more strings in english.lang use Title Case.
However, I
[EMAIL PROTECTED] wrote:
Date: 2008-06-05 10:20:39 +0200 (Thu, 05 Jun 2008)
New Revision: 17690
Log Message:
make %V a little simpler. only the x and y values have to be specified now (i.e
%V|0|0|| )
default values are as follows:
width - lcd width - the x value
height - lcd height - y
Jonathan Gordon wrote:
On 13/02/2008, Daniel Stenberg [EMAIL PROTECTED] wrote:
Except for the fun of doing all this, what's the big benefit with this in the
first place?
There needs to be a reason? It will be much nicer setting up the
config than having to find the find the setting in the
Jonathan Gordon wrote:
On 13/02/2008, Dave Chapman [EMAIL PROTECTED] wrote:
Wouldn't all those things also (with some effort) be possible on target,
and much more convenient?
i.e. context-sensitive help in the settings screens and improving the
structure/naming so users don't have trouble
All,
When trying to compile code for the TCC77x (arm946e-s core - an armv5
cpu), I got an error saying that my libgcc.a uses FPA instructions but
that my code did not.
After some googling, the problem appears to be that armv4 (our existing
ARM targets) and armv5 use a different floating
I'm also strongly in favour of keeping a single channel - I'm not that
annoyed by off-topic chat (I can easily ignore it), and very much like
the fact that the Rockbox community is one where there is no strong
distinction between devs and users - every user is encouraged to help
themselves and
Jonas Häggqvist wrote:
Dave Chapman wrote:
1) We start to incorporate GPLv3 code like espeak into Rockbox. Our own
any version license allows us to do that, but then Rockbox as a whole
would be GPLv3.
For the reasons Daniel gave in his very first response, I don't see this as
being
Daniel Stenberg wrote:
Well, that's your view but not the view of many others. See kerneltrap
and the GPLv3 flame fest on the Linux kernel mailing list.
Companies like Tivo have used GPLv2 fine for many years and they have
contributed their changes back and thus helped improving Linux. They
[EMAIL PROTECTED] wrote:
Date: 2007-09-05 01:29:42 +0200 (Wed, 05 Sep 2007)
New Revision: 14613
Log Message:
get experimental usb stack compiling
Modified:
trunk/firmware/target/arm/usb-fw-pp502x.c
Christian,
This commit breaks USB detection on at least my ipod video when
RaeNye wrote:
My advice would be to try and get other people interested - either existing
Rockbox developers who may
be interested in working on new targets, or (more likely to succeed) other
skilled Sansa Express owners.
BTW, try to check if the Sansa Express is similar (HW-wise) to
Brendon Costa wrote:
With that sort of information, how long do others think it might take me
to work on a port of rockbox if I say spend one or two hours a day on it?
As an example the Gigabeat F/X port took about a year from start to a
functioning Rockbox port, and the developers had
Basil Dozhdalev wrote:
Hello,
Had anyone ever try to develop Rockbox for Telechips-based MP3-players?
I wouldn't say I'm trying to develop Rockbox for the Telechips players,
but I do have such a device (a small flash-based MP3/WMA player with DAB
radio). This has a TCC773L.
I've been
Daniel Stenberg wrote:
On Sun, 22 Jul 2007, Dave Chapman wrote:
I was wondering what other developers thought about introducing the
concept of formal maintainers to Rockbox.
I think it sounds like a very sensible idea!
I've made a start on a MAINTAINERS file, which I'm appending
Hi all,
I was wondering what other developers thought about introducing the
concept of formal maintainers to Rockbox.
A lot of large open source projects seem to work this well - an example
is the ffmpeg maintainers list here:
http://svn.mplayerhq.hu/ffmpeg/trunk/MAINTAINERS?view=co
I see a
[EMAIL PROTECTED] wrote:
Modified: trunk/firmware/drivers/audio/tlv320.c
===
--- trunk/firmware/drivers/audio/tlv320.c 2007-06-11 13:32:29 UTC (rev
13619)
+++ trunk/firmware/drivers/audio/tlv320.c 2007-06-11 23:39:07 UTC
Dominik Riebeling wrote:
On 5/10/07, Martin Arver [EMAIL PROTECTED] wrote:
Do you think we should use this approach for all features not
supported by a certain target? Like sw/hw-codec stuff, color display
hmm, I think that would make the manual somewhat torn, which isn't
good either.
Christian Gmeiner wrote:
The big plus point is that we dont need to care about the simulator
with #ifdef's anymore as the simulator is a normal target.
I don't see how that will happen - won't it just mean replacing #ifdef
SIMULATOR with #ifdef SDL_TARGET ?
Looking at the current code, there
Christian Gmeiner wrote:
2007/5/10, Dave Chapman [EMAIL PROTECTED]:
I don't see how that will happen - won't it just mean replacing #ifdef
SIMULATOR with #ifdef SDL_TARGET ?
No you are wrong.. we will use the target tree feature:
firmware/target/sdl/*
How would adding a new target help
Dominik Riebeling wrote:
I rather think we should remove all themes from the svn builds and
rename the fonts package to extras package (or something similar)
that includes fonts and themes
Sounds a good idea.
We could also make the archived builds fullzip archives which include
both themes
Daniel Stenberg wrote:
On Mon, 17 Jul 2006, [EMAIL PROTECTED] wrote:
Gentlemen, we have sound on the 3rd Generation ipods. Thanks to
Daniel Ankers for debugging. It turns out the problem was simply that
we were calling the FIQ handler incorrectly - everything else was fine.
Jonathan Gordon wrote:
hey,
i was having a quick look through the bug reports and especially the
old ones have had no comments for 3+ months except asking weather the
bug still exsists.
How long do we wait for an answer before closing the reports?
Don't forget that Rockbox has been in
Simon M. wrote:
Maybe a developer with write-access to cvs could upload a version of
mp3_encoder.c with unix line endings please.
Done.
Hi,
I agree with the people saying that we shouldn't release 3.0 or come out
of feature freeze until it's ready.
But one of the problems, is that it isn't clear (at least to me), what
are the outstanding tasks that MUST be done before we are happy to
release 3.0.
So my suggestion is that we (in
Jvo Studer wrote:
gcc uclpack.o src/libucl.a -o ../uclpack
ld: archive: src/libucl.a has no table of contents, add one with
ranlib(1) (can't load from it)
make[2]: *** [../uclpack] Error 1
make[1]: *** [uclpack] Error 2
make: *** [tools] Error 2
I don't have the SH compiler installed on my
All,
I seem to recall that the moving of id3.[ch] and related higher-level
mpeg code from firmware/ to apps/ has been mentioned a few times, and
no-one seemed to object to the idea.
I did a quick test this afternoon, and tried to move the following files
from firmware/ to apps/:
id3.[ch]
Greg Haerr wrote:
: iPod Video
:
: Rockbox works on it, but there's no audio. No one seems to have worked
very
: hard yet at figuring it out. This probably takes some dissassembly.
Otherwise
: this of course resembles the Color and Nano models.
Why can't we use the code that the
[EMAIL PROTECTED] wrote:
and one of the most important principles you learn is to put the
user in the loop when you do interface design.
I so happy I'm not alone in this!
One better way would be to have polls on the rockbox site on these
issues, with
questions such as Do you have the
65 matches
Mail list logo
