Dominik Riebeling | 1 Mar 15:26 2008
Picon

Re: Plugging an Iriver H140 to a braille terminal

On Fri, Feb 29, 2008 at 7:50 PM, S├ębastien Hinderer
<Sebastien.Hinderer <at> ens-lyon.org> wrote:
>  Would it be possible to plug the braille terminal to the MP3 player in
>  place of the usual remote control ?

no, not without additional hardware / software.

>  Is the plug used to connect the remote control standard ?

no.

>  Any hope to go from this kind of plug to a serial or parallel one ?

well, you could add some self-built hardware to do that. The LCD is
connected using an SPI interface, the buttons use a resistor network.

>  Given that the braille display embeds Linux and is fully programmable,
>  this would allow one to use the terminal as a remote control, displaying
>  the information in braille and driving the MP3 player from the braille
>  keyboard.

well, you could build some hardware around the interface of the player
to interface with the braille. But I don't think this would be an easy
task. Yet interesting.

 - Dominik
Matthias Mohr | 1 Mar 19:10 2008
Picon

Build-Problems within cygwin

Hi everybody,

I always built my own rockbox versions within a cygwin environment.
This worked for years - but since a while I have several problems for which I need some help.

"make all" works fine

then I usually do a "make fullzip"
this now brings a lot of the following errors:
----------------------------------------------------------------------------------------------------------------
cp: omitting directory `/cygdrive/c/Prog/Projekt/RockBox/rockbox.orig/'
cp: missing destination file operand after `/cygdrive/c/Prog/Projekt/RockBox/rockbox.orig/icons/'
Try `cp --help' for more information.
----------------------------------------------------------------------------------------------------------------
(cp --version: cp (GNU coreutils) 6.10)

and also these two ones (BTW: the missing files do exist!):
----------------------------------------------------------------------------------------------------------------
Error opening file: /cygdrive/c/Prog/Projekt/RockBox/rockbox.orig/fonts/nimbus-12.bdf
Error opening file: /cygdrive/c/Prog/Projekt/RockBox/rockbox.orig/fonts/helvR10.bdf
----------------------------------------------------------------------------------------------------------------

It does not matter for which target platform I compile (I tried Sansa e200 & iRiver H300),
the warnings (errors?) always occur when calling "make fullzip"

Cygwin is up to date and rockbox is also an up to date SVN version...

Is the compilage with cygwin no longer supported or are there new limitiations with the
cygwin utilities or are this scripting bugs?
BTW, a "perl --version" returns this:
(Continue reading)

Marianne Arnold | 2 Mar 00:44 2008
Picon

Re: Build-Problems within cygwin

Matthias Mohr wrote:

> Cygwin is up to date and rockbox is also an up to date SVN version...
> 
> Is the compilage with cygwin no longer supported or are there new 

Compiling definitely still works for me under cygwin (using it commandline style and I admit mine's
probably not the very latest version). I remember someone showing up in IRC with the same problem as you
describe with the bdf files. The theory back then was that it had something to do with the usage of
TortoiseSVN which requires cygwin to be set up differently (line ending issues) - see talk with "przemhb"
in http://www.rockbox.org/irc/log-20080127.

I'm not sure whether he solved the problem or not but maybe this will give a first idea what to try.

Regards, Marianne.

Matthias Mohr | 2 Mar 13:20 2008
Picon

Re: Build-Problems within cygwin

Hi Marianne,

thanks for your help - I read the IRC talk with "przemhb", but my situation is bit different.
I definitly always used LF and not CRLF (I just checked, the bdf for example have unix line endings).
(and the build did work in the past without problems - so there must have something changed inbetween)

And I did not use ToirtoseSVN to checkout rockbox, I used the commandline svn from cygwin.
BTW, I did use TortoiseCVS when the repository was CVS - and it worked like a charm;
but the whole svn is a mess (even the command line version included in cygwin) - but that's another story

To be sure that my repository checkout is O.K. I tried to do a fresh checkout in an empty directory.
But that failes now:
-----------------------------------------------------------------------------------------------------------------------------
svn: Can't move 'trunk/rbutil/rbutilqt/.svn/tmp/entries' to
'trunk/rbutil/rbutilqt/.svn/entries': Permission denied
-----------------------------------------------------------------------------------------------------------------------------
(when I remove the whole directory again and reenter the "svn co svn://svn.rockbox.org/rockbox/trunk"
command, the output stops on a different place with the same error message)
What the hell is going on here...????

with regards,
Matthias

Matthias Mohr | 2 Mar 14:39 2008
Picon

Re: Build-Problems within cygwin

Hi everybody,

I solved my problem now - it seems that I also had mixed checkouts/updates
with TortoiseSVN and command line svn :-(

I also solved the checkout problem with the command line version by temporarily 
disabling my virus scanner (Avira Antvir) .
Don't know why this happened and if it'll happen again, but currently it workes again
and I'm happy :-)

Thanks for your help!

regards,
Matthias

Frank Gevaerts | 3 Mar 00:27 2008
Picon

logf over USB

Hi all,

It is now possible to get logf() output over USB on PortalPlayer 502x
platforms. For instructions on how to enable and use this, see
http://www.rockbox.org/twiki/bin/view/Main/PortalPlayerUsb#logf_over_USB_Serial

Frank

--

-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan

Daniel Stenberg | 3 Mar 22:22 2008

gsoc2008 - Organization Application [DRAFT]

Hello!

It is time to apply for becoming a mentoring organization for Google's Summer 
of Code 2008. I've taken the liberty of re-using last year's application 
heavily and adjusted them to this year. Attached is my draft for how to 
respond to the questions.

I'm open for feedback on both content and how it is phrased etc. Don't hold on 
to your comments very long though, since I hope to submit this in a few days.

-- 
  Daniel Stenberg -- http://www.rockbox.org/ -- http://daniel.haxx.se/
About Your Organization
=======================

1. What is your Organization's Name?

Rockbox

2. What is your Organization's Homepage?

www.rockbox.org


3. Describe your organization.

The Rockbox project started in december 2001 and in it we develop a complete
portable music player firmware replacement - including operating system, GUI
and application suite. Rockbox runs on a wide range of support platforms
including players from Archos, Apple (ipod), iriver, iAudio, Toshiba and
(Continue reading)

Jerry Van Baren | 5 Mar 00:17 2008
Picon

Re: gsoc2008 - Organization Application [DRAFT]

Daniel Stenberg wrote:
> Hello!
> 
> It is time to apply for becoming a mentoring organization for
> Google's Summer of Code 2008. I've taken the liberty of re-using last
> year's application heavily and adjusted them to this year. Attached
> is my draft for how to respond to the questions.
> 
> I'm open for feedback on both content and how it is phrased etc.
> Don't hold on to your comments very long though, since I hope to
> submit this in a few days.
> 
> -- 
>  Daniel Stenberg -- http://www.rockbox.org/ -- http://daniel.haxx.se/

Hi Daniel,

Here are a few mostly minor English tweaks.

[snip]

> 5. Did your organization participate in previous GSoC years? If so, please
>    summarize your involvement and the successes and failures of your student
>    projects. (optional)
> 
> We took part of the program last year (2007) in which we got four projects

s/in which we got four projects/in which four of our projects were/

> accepted. Over all I think gsoc2007 gave us a real boost and we learned a lot
(Continue reading)

Mike Giacomelli | 5 Mar 02:05 2008
Picon

Re: gsoc2008 - Organization Application [DRAFT]

I recommend talking up our achievements last year more so that we sound better:

5. Did your organization participate in previous GSoC years? If so, please
summarize your involvement and the successes and failures of your student
projects. (optional)

We took part of the program last year (2007) in which we got four projects accepted. We developed some code that was extremely useful to our project as well as to others. Our new fixed point WMA decoder has made rockbox more useful for our users, was incorporated into the Open Neuros project, and has attracted attention from other groups.  We also hope to see it included in ffmpeg once it is mature enough to be merged into their current decoder.  Our metadata buffering project led to support for album art in rockbox and paved the way for further improvements in our playback system.  Finally, the USB project took some initial steps towards for a flexible software USB stack which is currently under active development.  Unfortunately, one proje ct, a text to speech engine did not succeed.

Over all I think gsoc2007 gave us a real boost and we learned a lot about the progress and how to act as mentors etc to bring with us for this year. We hope that the experience we got will make all projects we get this year succeed!

Daniel Stenberg | 5 Mar 09:10 2008

Re: gsoc2008 - Organization Application [DRAFT]

On Tue, 4 Mar 2008, Jerry Van Baren wrote:

> Here are a few mostly minor English tweaks.

Thanks! And thank you Mike Giacomelli too for the section 5 improvement. Your 
updates were merged into the new version I attach here.

I think this is now food enough for submission, but I'll still wait another 
day or two in case someone else feels there's some nits to pick...

-- 
  Daniel Stenberg -- http://www.rockbox.org/ -- http://daniel.haxx.se/
About Your Organization
=======================

1. What is your Organization's Name?

Rockbox

2. What is your Organization's Homepage?

www.rockbox.org


3. Describe your organization.

The Rockbox project started in december 2001 and in it we develop a complete
portable music player firmware replacement - including operating system, GUI
and application suite. Rockbox runs on a wide range of support platforms
including players from Archos, Apple (ipod), iriver, iAudio, Toshiba and
SanDisk. We're 100% spare time contributors.

4. Why is your organization applying to participate in GSoC 2008? What do you
   hope to gain by participating?

We hope to gain interest from new developers, both in the software but also in
the community, while simultaneously getting good code and interesting
contributions to the project.

5. Did your organization participate in previous GSoC years? If so, please
   summarize your involvement and the successes and failures of your student
   projects. (optional)

We took part of the program last year (2007) in which four of our projects
were accepted. We developed some code that was extremely useful to our project
as well as to others. Our new fixed point WMA decoder has made rockbox more
useful for our users, was incorporated into the Open Neuros project, and has
attracted attention from other groups.  We also hope to see it included in
ffmpeg once it is mature enough to be merged into their current decoder.  Our
metadata buffering project led to support for album art in rockbox and paved
the way for further improvements in our playback system.  Finally, the USB
project took some initial steps towards for a flexible software USB stack
which is currently under active development.  Unfortunately, one project, a
text to speech engine did not succeed.

Over all I think gsoc2007 gave us a real boost and we learned a lot about the
process how to work as mentors, which will make us even more effective this
year. Out of the four projects, three succeeded. We hope that the experience
we got will make all of our GSoC2008 projects succeed!

6. If your organization has not previously participated in GSoC, have you
   applied in the past? If so, for what year(s)? (optional)

n/a

7. What license does your project use?

GPL

8. URL for your ideas page

http://www.rockbox.org/twiki/bin/view/Main/SummerOfCode2008


9. What is the main development mailing list for your organization?

rockbox-dev <at> cool.haxx.se, subscription info here:
http://cool.haxx.se/mailman/listinfo/rockbox-dev


10. Where is the main IRC channel for your organization?

#rockbox on irc.freenode.net

11. Does your organization have an application template you would like to see
students use? If so, please provide it now. (optional)

no

12. Who will be your backup organization administrator? Please enter their
Google Account address. We will email them to confirm, your organization will
not become active until they respond. (optional)

Linus?


About Your Mentors
==================

1. What criteria did you use to select these individuals as mentors? Please be
as specific as possible.

All full committers who volunteer are eligible to act as mentors - final
choices will be made after we have a list of student applicants, so that we
can choose mentors suited to the specific areas of the projects that are
actually being accepted.

The volunteering mentors all have many years experience of both the Rockbox
project as well as in depth knowledge of the source code and general concepts.

2. Who will your mentors be? Please enter their Google Account address
separated by commas. If your organization is accepted we will email each
mentor to invite them to take part. (optional)

not known yet

About The Program
=================

1. What is your plan for dealing with disappearing students?

We will be requesting that all students communicate with their mentor or the
project community at least once a week, to ensure that any disappearances or
falling behind gets noticed promptly.

We will invite and encourage the students to join and participate in the
community, in the mailing lists, IRC and forums so that they feel a part of
Rockbox and not something happening on the outside. This also reduces the risk
of them disappearing.

2. What is your plan for dealing with disappearing mentors?

All mentors are full committers, who have maintained a long term association
with the project. Outright disappearance is therefore vanishingly unlikely.

In case of mentors experiencing unexpected time pressure, the committer
community provides a large enough pool of potential volunteers that we should
be able to arrange cover.

We have a large pool of active and skilled project members that should be able
to cover temporary "outages" of individual mentors.

3. What steps will you take to encourage students to interact with your
   project's community before, during and after the program?

We'll inform the possible students that interaction with the project's
community will be considered a plus when selecting applications. During the
six weeks familiarization period, mentors will suggest and encourage students
to engage in design discussion about their chosen task.

Throughout the coding period, mentors will encourage students to make their
in-development code available for comment and review on a regular
basis. Everything in the Rockbox project happens online, in public forums etc
so and we will of course assume and insist that program participants join in
and follow this set tradition.

By mentoring the students into this world and style of acting, we hope that
they will see and understand the benefit of doing it this way and that they
will then continue doing so even after the project's completion.

4. What will you do to ensure that your accepted students stick with the
   project after GSoC concludes?

We have a set of mentors who act professionally and assist as well as we can
to help the students see the fun in open source hacking our way. We truly
believe that once they've got their feet wet and got the hang of some of the
internals, they too will see the light and will continue to contribute even
after this summer.

Gmane