Rockbox Development > New Ports

vibe 500 Packard Bell

<< < (2/8) > >>

b0hoon:
Hello developers, everybody,

I'm locally porting this player. Currently everything works except:

- RTC (i don't know yet where it is connected - GPIOs or I2C bridge)
- Record (i don't know which GPIO switches it to the line in or MIC or activates it)
- Plugins (for obvious reason - keymaps).

Before i'll be asking for adding it to SVN i must resolve my local problem with my linux and the wifi network. Currently i'm forced to stick with Mandriva 2007 (which has an older and improper version of SVN) because on the never distributions with the never kernels (no matter what distro it is: Mandriva, Gentoo etc) my wifi card simply don't work because of bad drivers for rt2500.

I think that this player is better with Rockbox on the board, than the Iriver H10 :).

torne:
Congratulations on the porting success!

You don't need svn to post patches to the bugtracker, which is where your new port should go for now. Commit access is given by invitation after we've had a chance to see someone's work.

b0hoon:

--- Quote from: torne on December 11, 2009, 07:22:39 AM ---Congratulations on the porting success!

You don't need svn to post patches to the bugtracker, which is where your new port should go for now. Commit access is given by invitation after we've had a chance to see someone's work.

--- End quote ---

Yes, i know but i was porting it through the last month or two, and a lot of things has changed since my version, so i'm forced to resync it somehow to the possible latest version, before i'll commit any patches. I don't want to access to svn directly yet. And in the moment my local svn version don't want to operate with the source, so i'm getting "unknown-date" version of Rockbox, i can't resync it and probably creating patches in this situation is impossible.

I must have a distro with a new svn and the working wifi driver, but that is what i must resolve myself and it not belongs to this forum :).

b0hoon:
Ok, the source is ready and now i must learn how to give it to you. It is a lot of code so may i just simply pack it (zip) and post it on the bugtracker as a patch? (directory structure with a new and changed files). Or do i have to do patches (diffs)? But what with the directory structure then?

pyro_maniac:

--- Quote from: b0hoon on January 13, 2010, 12:17:13 PM ---Ok, the source is ready and now i must learn how to give it to you. It is a lot of code so may i just simply pack it (zip) and post it on the bugtracker as a patch? (directory structure with a new and changed files). Or do i have to do patches (diffs)? But what with the directory structure then?


--- End quote ---

I think an svn diff to post on bug tracker is the best way.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version