Messages

1

Zaurus - pdaXrom / 1.1.0beta2 Feed

« on: April 30, 2006, 08:26:40 am »

Is there a feed around where I can download kathrin-1.1.0beta2-corgi.zip?
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

[a href=\"http://zaurus.spy.org/feeds/cacko/pdaXrom/1.1.0/beta2/c760/]http://zaurus.spy.org/feeds/cacko/pdaXrom/1.1.0/beta2/c760/[/url]

2

Zaurus - pdaXrom / Duke Nukem 3d For Pdaxrom

« on: March 11, 2006, 06:44:08 am »

I have suspiction to little big endians. We will see. Someone with better coding experiences than me  could look into it.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=118015\"][{POST_SNAPBACK}][/a][/div]

No it's not the endianess (arm is little-endian as x86), but probably the alignment issues. Arm can't correctly read/write words which are not aligned properly -- this is a major PITA for software porters.

3

Zaurus - pdaXrom / Keyboard Problems With Scite (and Gnumeric)

« on: November 25, 2005, 06:07:39 am »

For mc, you can just push Esc, and then 1-9 or 0, for F1-F9 or F10.

4

Zaurus - pdaXrom / Pcsx Port Here(pdaxrom Version)!

« on: October 16, 2005, 10:49:22 am »

i am not cross-compiling(by system glibc based while sdk is built to libc systems)
i used swap a 128M swap but i see this:
when compiling with -O setting draw.c takes forever eats all the memory and while doing it ,it goes for idle to full load like evry second.
when compiling without -O setting it takes a minute and i don`t even need a swap.

plz can someone tried to compile P.e.p.o softGPU on his Z with -O3 or -O4 setting?
src here:
http://prdownloads.sourceforge.net/peops/P...tar.gz?download
replace files using my patches.

plz plz someone try a native compile , i need to see if this is a problem that i only have


Uriel
[div align=\"right\"][a href=\"index.php?act=findpost&pid=99552\"][{POST_SNAPBACK}][/a][/div]

Cross-compiling would solve your problem. Z just doesn't have enough memory. Use of swap file gives the compiler an ability to continue working, but with the performance degraded to almost zero. So you can try using a bigger swap over NFS and leave it for a night  Cross-compiling is sure a better solution.

5

Zaurus - pdaXrom / Pcsx Port Here(pdaxrom Version)!

« on: October 16, 2005, 04:28:53 am »

i compiled Pcsx with patches based on Pcsx for X/qt which tewks for pdaxrom(the Pcsx for X/Qt will not work on pdaxrom!).

the problem is that i can not compile softGPU plugin with any -O setting!(which means no optimazions which means bad speed  ).
when compiling with a -O setting the compiler hangs on draw.c and eating all the memory including 128MB swap , i think that it is a gcc bug(laze and shasz check that plz).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=99531\"][{POST_SNAPBACK}][/a][/div]

Are you compiling on the Zaurus? The compiler can eat enormous amounts of memory when compiling large complex files, this is a normal behaviour. If you're compiling on the Zaurus, try using the cross compiler on a regular PC box.

p.s. If the swapping starts to occur, the compilation is almost always doomed -- you need more RAM then.

6

Zaurus - pdaXrom / pdf viewer for pdaxrom?

« on: September 26, 2005, 04:15:45 am »

Hi everyone, for those who want try another nice pdf reader, here are three package:

Great job! One note: I would suggest you uploading these right to the unstable pdaXrom feed. Contact Laze with the desired login/password, and he would create an account for you. All the packages in unstable feed came that way.

7

Zaurus - pdaXrom / Mplayer 1.1.5 & Fullscreen

« on: August 25, 2005, 04:08:28 pm »

however the avi I have will only play with

Code: [Select]

-nosoundat decent framerates. Good for silent movies but not much else. I'll have to try different sound encoding to find something that works. If anyone has anything that works please let me know
[div align=\"right\"][a href=\"index.php?act=findpost&pid=93228\"][{POST_SNAPBACK}][/a][/div]

Have you tried with -ac mad? Just in case...

8

Zaurus - pdaXrom / Keep Pdaxrom Alive

« on: August 18, 2005, 08:52:01 am »

My suggested method was an attempt as fairness, so that the developers get a monthly sum to develop the core as well as the user-centric side.

The bounty method deprives the developers of money to develop the core and opens up the money to other people. So the developers would be back to square one (penniless) and forced to attempt to claim the bounties faster than someone else in order to even have any money for core development.

If that's what it's going to take inorder to get what is wanted, who's in favour of with holding all future donations, drawing up a list of core things for a bounty process and then if the developers want our money, they can do what we ask of them? I really don't like this method, but if that's what it takes to be heard.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=92316\"][{POST_SNAPBACK}][/a][/div]

Ok, it seems you didn't understand. I am not talking about inviting any off-side developers to participate in the bounty system. I would like to remind you that here, in this thread we are trying to work out a finance problem the current pdaXrom developers (sashz and Laze) have. We are not talking about any other developers! We need to get sashz and Laze some money, ok? So, I suggest only sashz and Laze participate in the bounty system as developers. Not anyone else. So the bounty method doesn't deprive money, quite the contrary -- it draws it. That's what it is suggested for.

Second, the development of the core most certainly includes a set of tasks, just like a development of anything else. For instance, support for new model XXX, support for VFP (done already!:), support for xrandr extension (done already!:), support for xvidmode extension (well, I think this is one currently missing) -- these all are tasks (features) too. Answering to the question on who's in favor of drawing up list of these -- both developers and users. They both may file them. For instance, the developers may know what an 'xvidmode' extension is -- then THEY file a feauture request, describing what that is and what merits does it have -- and asking if that is needed, if there is a monetary interest. Both users and developers (developers = Laze and sashz at the moment, as I said) would do so.

When we talk about a bounty system, we don't talk about other developers. The goal is to draw money to the core developers, not to anyone else. The bounty system would do so. And the bountry system would cover any aspect of development. All of them.

There is no need for any commitee. I understand you would like to be a part of it, but that solely is not the reason to build one.

9

Zaurus - pdaXrom / Keep Pdaxrom Alive

« on: August 18, 2005, 06:31:38 am »

There is no need for any kind of a commitee. An open market would be much better: people demand something and offer to pay some sum of money for it -- developers look if it suites them. If people want games, that would be games. In this case, if developers wouldn't be interested in compiling games, the people who wanted 'em might decide to forfeit the idea, or to raise the bounty for the task instead. And so on. The developers may also initiate the proccess -- by offering some feature and looking if it is worth doing, if there is an interest. That's how the world lives, most natural and efficient.

I understand that this would not guarantee a particular $500/mo, but that would be depending solely on the developers, so they would need to be doing the best -- and then they could acually get above the mentioned $500 barrier. This is most fair for both the users and developers -- what is paid is for actual work on the actual demanding things.

10

Zaurus - pdaXrom / Status Update...

« on: August 17, 2005, 03:32:37 pm »

...
Then the comment function, bug reporting system and bounty system will probally be next. And the feeds with developers havin g 100% control for updating and editing. We will probally also make it so that the sources for the ipks can be uploaded for each - this should help people trying to compile a newer version etc.

Looks like a great beginning! I would like to just comment on some bits. First: bug reporting, feature requesting and the bounty system should be the same thing: that is, people either file a bug report or a feature request, and then it should be possible to put money on it, and to comment on it. Well I guess it is obvious, but just in case
Second: it would be really nice if the package maintainers upload ONLY the source, and the whole compilation task is done server-side. This way the migration to the new toolchains is automatic, there is no redundancy, the sources are always working for people who download them, and so on. This scheme is used on Debian and I guess in pretty much every other major distribution too. I understand this is no obvious task to implement immediately (you'd need to set the rules for the maintainers of how to arrange the source packages, put the compilation infrastructure up, think about security and so on), but just think a bit on it, maybe you'd like the idea

Overall, looks promising, just don't loose the momentum on your way to success

11

Zaurus - pdaXrom / Keep Pdaxrom Alive

« on: August 16, 2005, 08:24:42 am »

I hope you people don't mind too much if I write this in Russian -- well, I guess you do mind, but I'm just trying to make my message most clear, without any possible misunderstanding I occasionally get when a recepient of mine is trying to decipher something I enciphered , ok?

sashz, тут дело вот в чем. Люди будут жертвовать деньги, только если будут видеть, что это что-то меняет, что что-то происходит, что они не жертвуют их впустую. В данный момент проект pdaxrom, со стороны, по крайней мере, выглядит как полностью замороженный проект без следов какой-либо деятельности. То есть, ничего не происходит: за кучу времени вышел только один RC (хороший, кстати, но только один) -- и больше не произошло ничего вообще. То есть, вообще ничего. Текущий сайт не обновляется, о новом сайте речь вроде и шла, а воз и ныне там. Изредка Laze появляется на форуме и рассказывает о том, что идет напряженная деятельность, и что дескать отсутствие какой-либо информации о ней говорит только о ее напряженности. Но это же нонсенс полный -- люди поверят в напряженную деятельность, только если будут видеть ее результаты -- и чем больше, тем лучше! Но никаких результатов не видно. Так с какой целью люди будут жертвовать, если, несмотря на их предыдущие попытки, проект, наоборот, вообще остановился? Зачем жертвовать, если это ничего не изменяет? Люди при этом пробуют другую стратегию -- раз пожертвования никакого результата не приносят, то, может быть, будет получен какой-либо результат от их отсутствия?

Я что хочу сказать. Если действительно какая-то работа ведется, то она, или как минимум информация о ней должна быть постоянно доступна. Люди любят новости. Люди любят новые фичи. Люди вообще любят, когда что-то проиходит. Тогда при появлении новой фичи можно будет просить их о том, чтобы они чего-нибудь пожертвовали. Но куда лучше вообще сделать систему, где есть список фичей, и каждый желающий может персонально внести сумму, которую он даст за ее выполнение. По каждой фиче должен быть свой тред, в каждый из которых будут поститься апдейты о том, что с фичой происходит. Все эти апдейты также автоматом можно выносить в одну основную ленту новостей. Как только фича сделана, все положенные на нее деньги уходят команде разработчиков. Это будет гораздо лучше. Это вообще будет идеальным вариантом.

Можно также ввести подписку, но, думаю, это будет гораздо хуже.

В общем, коммуникация -- вот что ОЧЕНЬ важно. По сути, люди жертвуют за коммуникацию, частным случаем которой являются новые релизы -- но также и новости, и прочие вещи. А когда люди не жертвуют, а делают вклад в то, что им КОНКРЕТНО необходимо -- это вообще совсем хорошо. Я крайне настоятельно мог бы порекомендовать подумать над предложенной bounty-системой, где люди вносят вклады за фичи. По-моему, это было бы САМЫМ лучшим вариантом для проекта сейчас. Если же продолжать политику о том, что дескать, "нам нужны деньги, а дальше уж мы там сами как-нибудь", то проект, скорее всего, загнется.

Все это -- на уровне простого совета. Надеюсь, я достаточно адекватно смог высказать свои мысли. Спасибо за понимание.

12

Zaurus - pdaXrom / Opie-Reader uploaded

« on: August 03, 2005, 10:18:55 am »

ikm
Great. Could you share Makefile or build script?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88922\"][{POST_SNAPBACK}][/a][/div]

I've been offline for some time. I can send you the entire source with all small tweaks I applied, just provide an email to send to. I regret there is no such concept as a "source package" in pdaXrom, I think authors need to be required to provide them, and furthermore, the binaries should be built from them automatically, server-side, with the current toolchain and so on. Debian way, that is, the sane one

13

Zaurus - pdaXrom / Scummvm Patch Set?

« on: February 02, 2005, 04:29:09 pm »

Ok, here it is. The diff is against the original scummvm 6.0.1b source code.

14

Zaurus - pdaXrom / Scummvm Patch Set?

« on: January 27, 2005, 06:08:50 pm »

Hi,

Just build ScummVM 0.7 with FLAC/Vorbis and MPEG2 support. Works great.

Is there a diff or a whole source tree for the current 0.6 version on the unstable feed though ? It would be nice to add the menu button support back into 0.7.

- Andy
[div align=\"right\"][a href=\"index.php?act=findpost&pid=64054\"][{POST_SNAPBACK}][/a][/div]

Yes, I can diff it and send it to you. There are several things my version was different from the upstream:

1) click-on-release behaviour, so you don't accidentally choose the wrong dialog entry and mess up the story line;
2) suspend functionality, which turns off the sound subsystem before suspending and turns it back on after resuming -- that is the only way for suspend to work correct, else there would be no sound and the game would eventually freeze;
3) xrandr hacks for switching video resolutions (and also optionally rotating the screen 180 degrees to be more handy when the clamshell is closed);
4) keyboard keys acting as mouse buttons;
5) simon and bass alignment issues were fixed -- I imported the fixes from zports.sf.net;
6) some xmodmap key mappings, and probably other minor tweaks I can't remember right now.

This patch is a bit messy, of course, not meant for any kind of upstream integration -- just to make scummvm work nice on Z :) Just provide an email where to send it, and I'll do so. I don't have much time to devote to the Z world currently, so I would be glad if you would take the maintainership :)

15

Zaurus - pdaXrom / I Love It!!!!

« on: January 09, 2005, 03:10:20 pm »

...the Curse Of Monkey Island FULL SPEECH, with video FULLY WORKING, FULL SPEED on my zaurus.... geeeeeeeeeeeeeeee.... 640x480....

I had to share with you all my joy...

Great! I actually never thought the speed would be adequate enough, it used to be a bit slow with ScummVM even on a regular PC, so I never tried. How much space does it consume, where do you store it?