Hello all patient devs.
As you know, we've had some site issues the last month since I upgraded gerrit.
It has stopped calling any hooks and has resisted all my attempts at starting
again. There is to my knowledge no way to downgrade gerrit without losing the
last month of work, since the updat
Hi devs.
It has been brought to my attention that some of you may have ssh-dss keys
registered for access to Gerrit and since a server update a while ago you are
now denied access, while getting error messages that give very few clues.
The reason for the problem is that ssh-dss has been found t
Hans-Martin Mosner via rockbox-dev wrote:
> looks like the sender (ro...@bieberphoto.com) has had his mail account hacked.
I have now removed this account from the list.
--
Björn
Thomas Martitz wrote:
> Therefore I propose that we relax the typedef rule and allow
> typedefs for integral types (only) when reasonable. This would
> basically be adopting the Linux kernel guideline w.r.t. to typedefs,
There are times when typedefs are useful, but they are in fact exceptions. I
Ryan,
Your attached files were too big for the mail list handler to accept. I
uploaded them here instead:
http://download.rockbox.org/new-compressor/
Here is the text from Ryan's mail:
Here are some demo files. The artist is Iona, from the album
"Heaven's Bright Sun". It is a live
Ryan Billing wrote:
> To my own ears, the response is "alive", natural sounding.
> Percussive instruments become more bright, real.
Is it possible for you to prepare demo files showcasing the differences?
Obviously, it's best to try it on-device, but a demonstration would serve as
useful input i
Amaury Pouly wrote:
> A simple solution would
> be to prevent opening opening a file for writing for example.
Gracefully handling read-only media requires at least a thorough review of the
relevant file-writing code paths to ensure failure to write shows a (single)
sensible message to the user a
The archos recorder build has tipped over the limit for size, and now the
autobuild always fails.
The tipping point was commit bd6e6ed but the code has been growing steadily so
I wouldn't say this particular commit is any more responsible than others
before it.
Still, we need to fix this someh
Hi all.
I just realized I haven't informed you that the main Rockbox server will be
physically relocated today, causing a downtime of 1-3 hours.
It is planned to start at 09:00 CEST.
--
Björn
Frank Gevaerts wrote:
> I'm pleased to announced that Rockbox on my Ainol Novo 7 Paladin
> running Android 4.0.3 (ICS), which has an Ingenic JZ4770 MIPS CPU,
> successfully played its first track:
> Djungel, by Björn Stenberg
Wohoo, that was quick! Nice job!
--
Björn
Frank Gevaerts wrote:
> Thoughts?
I agree with your plan. Ask for one ID per target, make use of whatever we get.
As for buying our own ID space, I'm not sure I think that is the best use of
donations.
--
Björn
Amaury Pouly wrote:
> I'm pleased to announced that my Creative Zen X-Fi2 successfully played its
> first song:
> 2Pac - California Love
Great work!
--
Björn
Torne Wuff wrote:
> I propose that we do our best to switch to the following terminology
> consistently in our written materials:
>
> 1) "Stable release": e.g. stable release 3.10.
> 2) "Development build": e.g. development build abc123g.
> 3) "Archived development build": the daily snapshots Rock
Thomas Jarosch wrote:
> > I haven't enabled git commit mails yet. I hope to get to that within a
> > few days.
>
> Do I need a gerrit account to enable commit emails
> or is the feature not enabled yet?
Unfortunately it is still not activated.
--
Björn
asettico wrote:
> since the change to git, I did not receive anymore the commit
> notifications.
I haven't enabled git commit mails yet. I hope to get to that within a few days.
--
Björn
Torne Wuff wrote:
> Oops. I asked Zagor to move the old copy to the rockbox-old address,
> but I suspect that neither of us remembered to update the svn
> mirroring script to mirror to the new location :)
>
> Zagor, you need to do that; sorry for not thinking of it at the time :)
Done.
--
Björn
Robert Menes wrote:
> Nothing really builds yet; I'm still trying to figure out how to
> structure it and take out any unessential code.
Taking out code sounds like it will be difficult to merge your work with the
main branch?
--
Björn
Thomas Martitz wrote:
> >FS#12279 - Sansa Clip+: Music playback is returned to the head when wps is
> >changed since r30486
>
> The last one isn't easily fixable (according to jhMikeS), and I also
> don't consider it release critical (though it's technically a
> regression indeed).
The bug in th
Alex Parker wrote:
> Speaking of which, where are we with this? Any show stoppers people
> are aware of? Things that need focussing on?
We are in pretty poor shape, with a number of regressions. The way I see it, at
least the following bugs need to be solved before release:
FS#12310 - Crash whe
Jonathan Gordon wrote:
> Can this please be reverted? firmware/fonts.c should now know or care
> about the ui font at all, and post buflib fonts it doesnt.
> screen_access.c added a helper to set the font
> (screens[screen].set_font() ) which should be being used by the
> keyboard and lrcviewer.
I
Torne Wuff wrote:
> This is a first proposal of a git commit policy
It sounds perfectly reasonable to me.
--
Björn
Hello everyone.
We are now in feature freeze for 3.10. There are a number of issues open that
we need to fix before release, so please take a look in flyspray and see how
you can help.
--
Björn
Jonathan Gordon wrote:
> > Your objection as I understood it was that the patch does less than you'd
> > like, not that what it does is wrong.
>
> No, that's correct.
Then I think the commit can go ahead. This might only be a small part of what
some of us want to do, but the other parts (total m
Jonathan Gordon wrote:
> So one objection isnt enough? commit the sleep timer rework by all
> means, but dont move t&d unless the rest of the discusison is settled.
Your objection as I understood it was that the patch does less than you'd like,
not that what it does is wrong. If that is a misunde
Thomas Martitz wrote:
> Perhaps
>
> void lcd_puts(int x, int y, const char* text);
> void lcd_putsf(int x, int y, const char* fmt, ...);
> void lcd_putsf_ex(int x, int y, int xcrop, int style, bool scrolled,
> const char* fmt, ...);
Having both lcd_puts and lcd_putsf gives no advantage, on arm an
Dave Hooper wrote:
> There would need to be more arguments, if everything was unified into one
> function. In particular: for scrolling lines you need to know both the 'line
> number' and the coordinates (the scroll tracking doesn't work off
> coordinates along, it's a list currently indexed by lin
During my current adventures into android screen scaling, I have been looking
into our lcd api. It was a while since I dug into it last, and I was quite
intrigued to find that we now have no less than 14 lcd_puts function calls:
lcd_puts
lcd_puts_offset
lcd_puts_scroll
lcd_puts_scroll_offset
Jonathan Gordon wrote:
> > Fine, implementing this in the classic list until the skinned list is
> > ready to replace it sounds like a good plan to me.
>
> Doing that gives little motivation for someone to finish off the
> missing bits of skinned list
That is a risk, but I don't consider it great
Thomas Martitz wrote:
> I agree it's less than ideal that there are two list
> implementations, and I see the skin engine eventually taking things
> over.
> But as of now there just are two implementations, and the classic
> lists aren't going to go away very soon. Plus the skinned lists have
> bug
Rockbox on Android is a complex topic, subject to the interpretation and
expectations of each developer and user. Here is my view:
Android is a very different target from our hardware targets. On an iPod or a
Sansa, we are the masters of the device. We control everything. Nothing happens
withou
Thomas Martitz wrote:
> It is a separate patch, actually :)
I mean a separate patch discussion, and a separate commit.
--
Björn
Thomas Martitz wrote:
> I find an about menu in the main menu a nice fit.
It's rather unorthodox though. "About" is usually an option in the Help menu,
showing version and some basic credits. It's not where you find system or debug
information.
I think the time and timer setting changes are fin
Thomas Martitz wrote:
> This patch adds line padding to lists on touchscreens, in order to
> make lists reasonable useful without huge fonts.
The comments in this thread suggest the unskinned lists and the skinned lists
are not handled by the same code, and don't get the same behaviour. Is this
Jonathan Gordon wrote:
> 2) the only reason this is wanted at all is because Raaa doesnt use
> native lists. The effort shold be put into making native lists work
I disagree. I don't want to mix Android and Rockbox GUI elements in in this
version. For one, it would kill the skinning.
--
Björn
mat wrote:
> I would be happy to throw a few $$ to rockbox's way if this would help.
> I would really like to see this player functional (since my iriver broke,
> I've missed my colour screen!)
The tip jar (paypal account) is always open. :-)
--
Björn
Björn Stenberg wrote:
> It still feels like a "Rockbox emulator", rather than a full-blown android
> music player app.
After I posted this, Hayden Pearce urged me to try his cabbie theme
modification (FS#12254). And after seeing that, I am much more optimistic than
when I
Thomas Martitz wrote:
> Then 4.0 is vaporware. At least I see no movement towards an RaaA release.
> It still needs actions from the swedes (current build signing, market
> account).
I disagree. It is not the paperwork that is holding the android app from the
Market. It is the fact that it is sti
Alex Parker wrote:
> a) 3.10 or 4.0
> b) why?
a) 3.10
b) Because the user-facing changes are not big enough to warrant 4.0.
--
Björn
Bertrik Sikken wrote:
> I wonder if the rockbox fund can pay for a Sansa Clip Zip, so I can do
> further rockbox development on this player.
Absolutely. This is one of the core purposes of the fund.
The way we normally do it is you buy the player and then we refund you the
money. If there are di
On this friday the 9th, there will be some server downtime due to maintenance.
We are migrating all services to a new faster machine.
Estimated time for the work is 13:00 - 15:00 CET. This downtime will affect
pretty much everything except the forums: www, svn, git, logbot and build
server.
--
Thomas Martitz wrote:
> I have one question: If I had 1 or 2 fellow students that would
> possibly want to attend too (not Rockbox dev, but they listened my
> presentation and are users and also technicians and very nice guys
> and they love London), would the fund be able to help them too?
No. Th
Alex Parker wrote:
> I suggest that this be a week after Torne sent the original message,
> so this Tuesday coming.
Sounds good.
--
Björn
> Op 11-11-10 12:18, Teruaki Kawashima schreef:
> >>+/* this are not actually the correct dimensions (480x272 is correct)
> >>+ * should be fixed once there's a working LCD driver */
> >>+#define LCD_WIDTH 480
> >>+#define LCD_HEIGHT 272
> >>+#define LCD_DPI128
Maurus Cuelenaere wrote:
> See
Alex Parker wrote:
> 1) Release manager.
> Frank Gevaerts and myself have declared ourselves willing
Very good initiative. I agree two people is better than one for this role. And
I can't imagine any better candidates than you two.
> 2) Release calendar
Good idea. I'll set up a rockbox google
Thomas Martitz wrote:
> I think we should work a lot more with RC builds to let users test
> on targets for which we don't currently have a maintainer around.
I agree, but providing RC builds alone is not very useful. We need to help the
users with their testing. And we need to help users report
Compared to most other open source projects, we have quite a large number of
committers. And in addition to that, we have a healthy number of people
submitting patches and bug reports.
However, in contrast to pretty much every other open source project out there,
we don't have a project leader.
Maurus Cuelenaere wrote:
> I was wondering, how do you plan to handle the different screen
> dimensions at runtime? For some platforms this isn't needed (Maemo only
> has N900), but for others this is a requirement (Android, WinCE,
> iPhoneOS, ..).
Android supports resolution specific resources, s
Bryan Childs wrote:
> I think he got a bit fed up with trying to fix up bits of the CSS / HTML to
> make it work properly across all screen resolutions.
That was not actually the big issue. What has made me push the new design down
on my todo list is simply that I suck at web design. And the des
Jonathan Gordon wrote:
> This has been brought up before about getting a blog or something
> going, I thought the consensus was yes do it, but it needs someone to
> get it actually going.
I can set it up, but the current front page is a mess. Adding a blog to that
sea of information isn't going t
Andrew Poelstra wrote:
> What version of gcc will be the "standard" for eabi builds?
>
> I (and others, I assume) prefer to build my own tools so that
> when things go wrong, at least I know what the situation is.
If you prefer typing "configure" and "make" yourself, please use the same
options a
One of the discussions we've had during the developer conference was about the
Rockbox Steering Board. Do we need it? Can it be improved? How should it work?
The consensus was that the steering board is a useful institution that we all
want to keep. Its' purpose is to be a last resort in case di
Björn Stenberg wrote:
> After you have built the new gcc, add "arm-eabi-gcc444" to the -archlist
> parameter in your runclient.sh script.
I forgot: You also need to restart the runclient.sh script (not just
rbclient.pl) for the changes to take effect.
--
Björn
Hi builders.
We will soon be moving some builds to the arm-eabi compiler. That means we need
build clients with it installed. So if you haven't already, please run
tools/rockbodev.sh (as root, normally) and choose 'e' to build and install it.
I have changed rockboxdev.sh a little so it now inst
Bryan Childs wrote:
> Ah, no you're not. It's still broken at the moment.
Fixed now!
--
Björn
Rafaël Carré wrote:
> OK for moving them to unstable category?
I say OK.
--
Björn
Jonathan Gordon wrote:
> This will break all existing skins so I'm planning on making a script
> to convert,
Would it be a good idea to add some type of versioning token to enable the code
to automatically inform the user that the wps he's trying to load is outdated?
--
Björn
Manuel Dejonghe wrote:
> I am currently looking for a distributed build system that suits the
> needs at my workplace, and I think the (new) rockbox build system fits
> snugly.
Nice. I too have recently been toying with idea of generalising the build
system to suit other project. I will be intere
Rafaël Carré wrote:
> The goal was just to have daily builds listed on the daily builds page
> (they already existed anyway) so we can get some feedback from users who
> test different revisions.
>
> I didn't modify the front page for the reason you give (to which I
> agree)
All builds are linked
Hi.
I have set up a new mailing list 'rockbox-rbclient' that I would like all of
you running build clients to subscribe to:
http://cool.haxx.se/cgi-bin/mailman/listinfo/rockbox-rbclient
The purpose of this list is to have a simple line of communication where I can
inform about new things.
An
Jonathan Gordon wrote:
> WPS tags should NOT be in the manual.
> 1) its too bloodu long which scares people away from reading it (yes
> its in an appendix but still, seeing 100+ pages is enough to turn
> people off)
We already have 10 pages of WPS tags in the manual. Unless we decide to
completel
Jonathan Gordon wrote:
> actually thinking about it, the only users which will be effected
> negativly are those who have the statusbar disabled *and* use the
> fm./rec screens *and* actually want the bar there... so about 3
> people...
If that is the case, I don't see any reson not to commit.
Sa
Thomas Martitz wrote:
> Could we use the build system for that?
Yes we could, but I consider that step #2.
--
Björn
Frank Gevaerts wrote:
> - We provide a feedback template that helps people figure out what needs
> testing, and to ensure that the resulting reports are reasonably easy
> to handle.
I believe we talked about something similar during devcon, didn't we? Anyway, I
completely agree.
However rath
Bob wrote:
> I am pleased to announce that the mini2440 can now play audio. The
> first track played was Dancing Queen - ABBA.
Congratulations!
--
Björn
Thomas Martitz wrote:
> I think the lcd glitches and lack of recording is already enough for
> keeping it in unstable. Then we also have poor battery life compared
> to the OF (IIRC ~15h vs (rated, I think nobody really tested it) 24h
> on the Fuze).
> [...]
> IMO stable should have a complete feat
Hi all.
Tomorrow thursday I will be taking down the subversion server (svn.rockbox.org)
for hardware upgrades.
Estimated downtime is 08:00 - 09:00 CET.
--
Björn
Thomas Martitz wrote:
> It looks weird, indeed. But it shouldn't have been called
> nat_toupper in the first place imo but something more generic
> instead.
Then change it. There is no point in keeping confusing code for historical
reasons.
--
Björn
Hi all.
Due to a bug, all build clients have hung and need to be manually restarted.
Just stop and restart it. "pkill -f rbclient.pl" will do fine.
--
Björn
As many of you know, I and Daniel have been working on a new distributed build
system since Devcon. It has now reached the point where it does everything the
old system does, only faster and better.
Hence, we intend to switch to the new system this evening (maybe sometime
around 20:00-21:00 UTC
samuel pattuzzi wrote:
> How about improving the usability of the interface?
It's a good ambition, but a poor GSoC project. A GSoC project should have well
defined limits so the student has a chance of actually completing it.
Also, the user interface is one of those areas where consensus is diff
Matt Reath wrote:
> Should I just grab a copy of the latest source, hack away, submit a patch?
That sounds like a great start. Hanging out in the IRC channel while working
can help you quickly get up to speed on things.
--
Björn
Mark Allums wrote:
> Would Rockbox be suitable for an iPhone app?
No. The Apple code signing scheme is incompatible with the GPL, meaning you
could only run Rockbox on jailbroken iphones.
> Would Rockbox be suitable for Google's Android?
Android currently only supports Java application. Porting
Maurus Cuelenaere wrote:
> But the point of all this is that you don't really need to look stuff up in
> plugin.h anymore, but rather use the documentation output for that.
Does anyone really want to do that? Seriously?
I'm all for making the code easy to understand, but I'm not so sure flooding
Peter D'Hoye wrote:
> what's the impact of the reduced speed on boost ratio and performance? Or
> was there nothing yet tested regarding performance?
I expect it will boost more since CPUFREQ_NORMAL is less than half of that in
SVN. But I think the average MHz is likely to be lower than SVN. I te
Robert Menes wrote:
> What's the Flyspray number? I'll try it on my H340.
It's in the title. :-) FS#9797.
--
Björn
Currently, boosting on coldfire involves waiting for PLL lock which can take as
much as 10ms.
This patch changes the boosting to just toggle the clock divider and not change
the PLL frequency, and thus not having to wait for it to stabilize. This makes
the boost near instantaneous.
The MCU524
Dominik Riebeling wrote:
> Also, those settings have been there since years and I don't see a
> point in removing them at all.
The point is that the fading code is ballooning. As we add the feature on more
targets, we have to add more conditions and settings due to different targets
implementing
Andrew Mahone wrote:
> I think it needs wider consideration before commit
On one hand I don't like it, because it introduces "magic" and obscures some
information.
On the other hand I like it, because it centralizes what every plugin is
alreday doing anyway.
What I am missing is a bit of elab
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 as the default? Becau
Paul Louden wrote:
>> Backlight timeout
> I think 30 seconds is way too long for a feature that's one of the
> biggest battery uses. Maybe 7 or 10 seconds, but 30 seconds will burn
> through a significant chunk of battery on players like the Nano.
Will it, really? Do we have any hard data on t
There are a couple of settings I would like to change the default values for,
before we ship 3.1:
Backlight timeout
The default five second timeout is annoyingly short on players with
backlight-off-unreadable screens. I think a default of 30 seconds is
reasonable. After all backlight is a
y_uchida...@infoseek.jp wrote:
> Yesterday, tools/database committed.
Yeah, this was part of an ongoing tools cleanup effort. There was a target in
tools/Makefile to build 'database', but it failed horribly so I spent a little
time fixing it.
I have looked at your patch #9371 and I think it's g
Marc Guay wrote:
> Just a quick idea to throw out there: The steering board has a weekly
> patch review meeting where they take a popular patch that's been
> sitting in the tracker for a while (multifont, bmp resize, snc viewer,
> etc), give it a thorough analysis,
A "patch of the week" effort is
Jonas Häggqvist wrote:
> Why are the ads not marked as ads?
Mea culpa. Frankly I thought they were so obvious that it wasn't needed. I've
added a header now.
--
Björn
Timo Horstschäfer wrote:
> Voting seems to be still activated, there's even a list of the most wanted
> tasks [1].
No the feature is not disabled completely since there is no such option in the
software. I have simply hidden the voting link from the task details page.
I don't want to change the
pondlife wrote:
> Can we also disable the "Add Vote" link? It might confuse people...
Done.
--
Björn
alex wallis wrote:
> I was just wondering whenever we click a link on the patch tracker to look
> at the details of an individual patch, there is always a line that says
> votes then a number.
> does that mean we can vote if we like a particular patch?
No. It means the software (Flyspray) suppor
Marianne Arnold wrote:
> Thing is that it looks easier in the beginning and might hold true for the
> few plugins with the most basic controls (4 directions, fire, off) - the
> trouble starts when the controls need more or even less than this or the
> game "layout" is a bit different.
I agree w
Hi all.
We received a "Cease and Desist" letter from a law firm representing The Tetris
Company, which holds the trademark "TETRIS". They claim our "Tetrox" plugin
infringes on their trademark "Tetris" and demand we remove it.
After consulting US and Swedish lawyers, I have decided to abide th
Hi all.
It is with mixed emotions I hereby announce that the feature freeze for 3.0 is
now lifted -- without 3.0 having been released.
We have been in freeze for over three months now. And we have indeed fixed many
bugs, but we still have critical problems that prevent a 3.0 release. With
summ
[EMAIL PROTECTED] wrote:
> Actually, I learned there is a drop-down (if you're logged in to
> Flyspray) to show "tasks reported by me", which allows me to see my
> patches.
Ah, lookie there! You learn something new everyday. :-)
Also, I noticed the "Reports" function allows date searching of th
[EMAIL PROTECTED] wrote:
> I want to do some simple things with the Flyspray bug tracker, and I
> can't:
> * look up my own patches
> * search patches by (sub)string of the attachment (e.g., I know the
> custom font patch exists, but I can't find it)
> * search by attachment date (e.g., I know cu
Daniel Stenberg wrote:
> I take it the good Dave has not responded since?
Correct, he hasn't. I will post any new development to the list.
--
Björn
fusion in
> the market as to whether the game was developed, published, or officially
> licensed by by PopCap Games. This current situation with the gem graphics as
> shown on Rockbox.com only perpetuates this confusion.
>
> Best,
> Dave
>
>
> -Original Messa
Here is Daves reply to my question. I have not replied back to him yet.
- Forwarded message from Dave Haas <[EMAIL PROTECTED]> -
Date: Mon, 17 Apr 2006 15:44:38 -0700
From: Dave Haas <[EMAIL PROTECTED]>
To: Björn Stenberg <[EMAIL PROTECTED]>
Cc: Rockbox development
S
Christopher Woods wrote:
> @ Björn or anybody else concerned, has there been any further action in
> this?
No. I will post to the list if/when anything happens.
--
Björn
essary, we will enforce our rights to the fullest extent of the law.
>
> Thank you for your prompt attention to this matter. I await your
> response.
Hi Dave.
My name is Björn Stenberg. I am the founder and one of the leaders of the
Rockbox open source project. I am also the owner and admi
Brandon Low wrote:
> I think that button processing can't be going through lists like that,
> too slow.
I'm not so sure. Buttons are pressed rather rarely (from a system/cpu point of
view) and the lag cause by looping through a few dozen entries will probably
not be measurable, let alone noticea
mathew holton wrote:
> Just wondering why my (maybe not so) fantastic asteroids plugin hasn't
> been added into CVS.
Which patch is that? I searched for "asteroids" in flyspray but came up empty.
--
Björn
Bluechip wrote:
> How about the legalitites of including an unlicensed MP3 codec?
As I'm sure you are aware, our MP3 codec is licensed under GPL which we respect
fully. Hence, no unlicensed MP3 codec.
If you are referring to patents, we have repeatedly acknowledged that this may
become a thorny
1 - 100 of 107 matches
Mail list logo
