summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--www/irc/rockbox-20020326.log591
1 files changed, 591 insertions, 0 deletions
diff --git a/www/irc/rockbox-20020326.log b/www/irc/rockbox-20020326.log
new file mode 100644
index 0000000000..3180ece155
--- /dev/null
+++ b/www/irc/rockbox-20020326.log
@@ -0,0 +1,591 @@
1Zagor => Björn Stenberg
2linus => Linus Nielsen Feltzing
3Bagder => Daniel Stenberg
4Wavey => Stuart Martin
5alkorr => Alan Korr
6adiamas => Rob
7
8**** BEGIN LOGGING AT Tue Mar 26 07:47:01 2002
9
10--> Bagder (~daniel@as3-3-2.ras.s.bonet.se) has joined #rockbox
11--- devlin.openprojects.net sets mode +n #rockbox
12--- Bagder sets mode +t #rockbox
13--> adiamas (~adiamas@as5300-9.216-194-23-156.nyc.ny.metconnect.net) has joined #rockbox
14<Bagder> hi
15<-- adiamas (~adiamas@as5300-9.216-194-23-156.nyc.ny.metconnect.net) has left #rockbox ("Client Exiting")
16--> adiamas (~adiamas@as5300-9.216-194-23-156.nyc.ny.metconnect.net) has joined #rockbox
17<adiamas> hey there.
18<Bagder> morning ;-)
19<adiamas> hehe for you ;)
20--> wavey (~wavey@dlan1431.dircon.co.uk) has joined #rockbox
21<Bagder> g'day wavey
22<wavey> howdy
23<adiamas> howdy wavey
24<wavey> hey adiamas
25<wavey> you have the recorder or player, adiamas?
26<adiamas> recorder
27<wavey> cool
28<adiamas> got it off of ebay for a nice cheap price.. :)
29<wavey> does yours have any quirks?
30<adiamas> one that ive noticed so far...
31<wavey> mine has dodgy contact in earphone socket
32<wavey> keeps resetting when moved :(
33<adiamas> if i remember correctly it was that i couldn't save the playlist...
34<adiamas> if i edited it when i was running.
35<wavey> only 3 months old
36<adiamas> from the player...
37<adiamas> if i do it from the command line, then transfer the file, all is well..
38<wavey> yeah
39<adiamas> well.. that and i had it completely barf on me last night.
40<wavey> i think that's normal crappy firmware
41<wavey> really?
42<adiamas> nod
43<wavey> recoverable, i hope?
44<adiamas> dunno what it was...
45<adiamas> yeah.. but i had to boot into windows to delete the disk.. clear it all out.
46<wavey> tsk
47<adiamas> i tried for like 4 hours in linux.. did everything i could think of...
48<adiamas> fsck
49<adiamas> fdisk
50<adiamas> fsck.vfat
51<adiamas> rm -rf
52<adiamas> hell, i even went as far as bit permisions...
53<adiamas> no go.
54<wavey> but windows was cool with it?
55<wavey> scary
56<adiamas> nods
57<adiamas> i did the windows "fake format"
58<adiamas> delete all :P
59<wavey> heh
60<adiamas> so badger.. how about setting a topic eh?
61<adiamas> :)
62--- Bagder gives channel operator status to adiamas
63<adiamas> heheh
64--- Bagder gives channel operator status to wavey
65--- Bagder has changed the topic to: rock the box
66--- adiamas has changed the topic to: rock the box http://bjorn.haxx.se/rockbox/
67<adiamas> hehehe
68<adiamas> so im waiting on addition to sourceforge to toss up version one of the FAQ
69<Bagder> cool
70<wavey> haven't read email yet - how far is your simulator going, bagder?
71<Bagder> I didn't do much more yesterday
72<Bagder> I'm gonna attack the font code next
73<wavey> cool
74<Bagder> to make a function that outputs similar text on the recorder and X11
75<wavey> groovy
76<Bagder> hm, not similar, identical really
77<wavey> even better
78<Bagder> Jerome Kuptz posted on the list and volounteered to write a windows port for the ui sim
79<wavey> lovely
80<adiamas> bagder you have any source i can grab to look at the sim?
81<Bagder> I added the sources to the rockbox CVS yesterday
82<Bagder> its easiest to get them off there
83<adiamas> k... ill go look
84<Bagder> it isn't very much to look at yet though ;-)
85<Bagder> it pops up a window, draws a line and outputs a text
86<adiamas> itll get there ;)
87<Bagder> adiamas: did you by any chance do some X11 programming before?
88<adiamas> nope.. but im a quick study.
89<adiamas> some mild exp with qt
90<adiamas> my modem is going to explode with all these downloads :)
91<Bagder> it's good to keep it busy ;-)
92<adiamas> yup.. esp just before i head off to bed ;)
93<Bagder> Gary's lcd code keeps a full copy of the bitmap in memory, and writes the whole thing to the lcd all the time
94<Bagder> which probably makes it easier to make a X11 version too
95<adiamas> that would make sense...
96<adiamas> has anyone finalized at all on what exactly our first target/goal is to achieve?
97<Bagder> not really, no
98<wavey> i think we need to produce a simple menu UI first
99<wavey> get that working on both player and recorder
100<adiamas> nods
101<wavey> and then look at how to approach the diff UI capabilities of the two devices
102<adiamas> some kinda lib that makes ui creation pretty simple would be nice
103<wavey> aye
104<adiamas> i havne't played with just the player.. so i don't really know the differences yet...
105<adiamas> oh.. btw ... when i post things.. forgive the spelling... i am a HORRID speller...
106<adiamas> put my mother (english teach for 20 yrs) into fits of tears :)
107* adiamas swells with pride
108<wavey> player has tiny screen
109<wavey> 3 lines or something like that
110<wavey> instead of 8
111<wavey> getting a simple menu ui up and running allows the back-end firmware developers to test their stuff
112<adiamas> ahhhh
113<wavey> so we need a) screen drawing capabilities
114<adiamas> ummm.. using cvs, how do i do a pull of all files in a dir?
115<wavey> b) file browsing capabilities
116<wavey> (to locate a file to play and stop, etc)
117<Bagder> adiamas: see http://sourceforge.net/cvs/?group_id=44306, replace "modulename" with uisimulator
118<adiamas> good.. just did that...
119<wavey> and c) basic controls to start, stop, pause an mp3
120<wavey> the 2nd generation UI can have the visual goodies - levels, scrolling titles, etc
121<wavey> the simple ui shouldn't take too long
122<adiamas> okay.. explain to me.. WTF would sourceforge require use of ssh1 when its known to be flawed?
123<adiamas> when not go to ssh2?
124<wavey> flawed doesn't mean useless
125<wavey> i guess
126* adiamas nods
127<adiamas> um Bagder you do realize your FILES lists a README, but there isn't one right?
128<Bagder> oops
129<adiamas> and just a question of taste... are we doing 2, 4, or 8 char tab stops?
130<Bagder> I do 8 char tab stops, c indenting with 2 spaces
131<adiamas> nods
132<Bagder> (setq c-basic-offset 2)
133<Bagder> (setq indent-tabs-mode nil)
134<Bagder> :-)
135<adiamas> i lean toward 4 myself.. but as long as i can map emacs to you im good :)
136* adiamas curses rh7.1
137<adiamas> friggin X11 headers are missing.
138<adiamas> hehehe yup
139<adiamas> or
140<adiamas> :set tabstop 4
141<adiamas> :set tabstop 8
142<adiamas> if you use a real _editor_
143<Bagder> hehehe
144<Bagder> hm, I wonder if using XDrawPoints() is sensible to use...
145<Bagder> I removed the FILES file now
146--> Zagor (~bjst@labb.contactor.se) has joined #rockbox
147<Zagor> yo boys
148<Bagder> morning
149<Zagor> have you looked at the new "mods" page I added to the web page?
150<Bagder> great sets of pics! ;-)
151<Zagor> thanks
152<Zagor> i should be a model! :-D
153<Bagder> btw Zagor, I think I go with Gary's fonts and his way of representing the lcd in memory
154<Zagor> ok
155<Bagder> the bytes are then vertical, lsb on top
156<wavey> zagor: nice pictures
157<Zagor> can you have >8 pixel wide chars?
158<Zagor> or high, i mean
159<Bagder> Well, we'll have a complete 112x64 pic in memory so we can make whatever we want
160<Zagor> thanks, wavey
161<Bagder> we write the complete bitmap
162<Bagder> at least to start with
163<Zagor> bagder: so why do we want vertical bytes? it ends up as a lot more bit flipping to get the pixels out
164<Bagder> because that's how the lcd itself has them
165<Bagder> makes faster updates
166<Zagor> ok, so the 112x64 pixmap is vertically oriented?
167<Bagder> each byte is 8 pixels "high", byte 0 is top left, byte 1 is 2nd left etc
168<Zagor> ok. makes sense, then
169<Bagder> I'm making three files now, lcd.c with generic lcd stuff, lcd-recorder.c that writes the bitmap to a recorder and lcd-x11.c that writes the bitmap to an x11 window
170<adiamas> were staying c based for now correct?
171<Zagor> yes
172<Bagder> yes
173<adiamas> or are we going straight to c++?
174<adiamas> k...
175<Zagor> no :)
176<adiamas> damnit... way to early here... can someone remind me the name of the file that allows you to turn services on and off?
177<adiamas> i konw its not /etc/services
178* adiamas needs bed bad
179<Zagor> uh, redhat?
180<Bagder> /etc/inetd.conf ?
181<adiamas> thats it.. thank you.
182--- Bagder gives channel operator status to Zagor
183<Zagor>
184--- adiamas is now known as adiamas|sleeping
185<Bagder> hey
186<Bagder> it works ;-)
187<wavey> what does?
188<Bagder> my new code, using a memory bitmap and lcd_update()
189<wavey> nice one :)
190<Bagder> exact same pixel-setup as the recorder would get
191<wavey> coolio
192<wavey> very useful
193<Bagder> very tiny letters though :-)
194<Bagder> I should probably allow some zooming or somthing
195<Bagder> so, now we can write a small program using the new lcd API, and the output seen in the X11 window is what will be seen on the recorder screen as well
196--> Tumm (coyote@dreamhosted.borlange.se) has joined #rockbox
197<Tumm> lo
198<wavey> excellent
199<wavey> hiya tumm
200<Bagder> hi
201<Bagder> XDrawPoints() was all I needed
202<wavey> well, technically, XDrawPoint() is all you needed ;)
203<Bagder> right, but one at a time turned out very slow
204<wavey> :)
205<wavey> surely XDrawPoints() uses a lot of XDrawPoint()?
206<Bagder> I'm running my X11-windows over ssh from a machine far away ;-)
207<wavey> or is that naive?
208<wavey> ah
209<wavey> heh
210<Bagder> well, it doesn't make them appear one by one, but instead all at once
211<Bagder> and it makes a huge difference
212<Bagder> time to eat
213--> alankrr (jbcoax@srs03v-7-104.n.club-internet.fr) has joined #rockbox
214<alankrr> hi people
215<wavey> happy fooding.
216<wavey> hiya alan
217<alankrr> oh yes i forget ! :) it's time for eating
218<wavey> :)
219<alankrr> i wonder why zagor doesn't reply
220<alankrr> but now i know
221<alankrr> ok what's up ?
222<wavey> daniel's ui simulator is coming along
223<wavey> he's got the same images appearing in X as will appear in the recorder lcd
224<alankrr> yes but is it using the same layout ?
225<wavey> including characters, i think
226<wavey> layout?
227<alankrr> i mean the way to set a pixel in LCD
228<wavey> you mean the API?
229<wavey> i think that's the idea
230<alankrr> ah ok it's just at the high level
231<wavey> X is just an output alternative, the recorder's lcd is another
232<wavey> the API is the same
233<wavey> hopefully ;)
234<alankrr> well, there are ways to put images at pixel coordinates
235<alankrr> but ye must use a shifter table
236<alankrr> 'cause shift instructions on SH1 are not smart enough
237<wavey> ah
238<alankrr> so it is why i asked if this simulator works by simulating the LCD layout on X
239<alankrr> but never mind, it is not an urgent thing to do :)
240<alankrr> you are the only one here ?
241<wavey> at the moment, yep
242<wavey> the swedes are having lunch, it seems
243<alankrr> and how many time will Bagder and Zagor be here in ?
244<alankrr> yes it's normal
245<wavey> try again in an hour or so
246<alankrr> okay see you all later
247<-- alankrr has quit ()
248--> alankrr (jbcoax@srs07v-5-60.n.club-internet.fr) has joined #rockbox
249<alankrr> are people still absent ?
250--- alankrr is now known as alkorr
251<Bagder> back
252<alkorr> oh good
253<alkorr> maybe you don't know me ?
254<Bagder> no I don't, who are you? ;-)
255<alkorr> arf, i know you brother in fact :)
256<Bagder> we're all a big happy family here anyway! ;-)
257<Bagder> btw, the lcd "simulator" is based on the original working recorder lcd code by Gary Czvitkovicz
258<Bagder> so it should work pretty much already
259<alkorr> yes i know, i've just reread your emails
260<Bagder> and I'm working on getting the same API to work on both the recorder and X11
261<Bagder> and I hope to do a similar dual approach for jukebox/X11 output later
262<alkorr> well it would be very difficult :)
263<Bagder> why?
264<alkorr> with just 2 lines with only 11 characters
265<Bagder> yes, then I'll make a small X11-windows 2 lines high, 11 chars wide. that's not too difficult
266<alkorr> and each characters are seperate with at least 3 pixels
267<alkorr> so you are very limited for fx
268<Bagder> I know
269<Bagder> but that's what we have, that's not anything I can do to change
270<alkorr> for example, scrolling can only be done on basis of characters not pixel
271<Bagder> yes
272<alkorr> etc.
273<Bagder> why is that difficult then?
274<alkorr> because it is a character-LCD not a graphical LCD
275<Bagder> I'm not planning to make one single unified API for both platforms
276<alkorr> ok
277<alkorr> anyway we need a begining for a start ;)
278<Bagder> true
279<alkorr> by the way, i know very well the SH1
280<alkorr> its advantages and disadvantages and its on-chip peripherals
281<Bagder> that's useful indeed. I've did my share of SH1 assembler, but that was some 6 years ago now
282<alkorr> :)
283<alkorr> gcc doesn't generate very well code as ia32 does :(
284<alkorr> let me explain to you
285<alkorr> there are two possibility to branch
286<alkorr> one is using jsr or jmp with a register containing the address to call or to jump
287<alkorr> another one using bsr or bra with an 12-bit immediate offset
288<alkorr> gcc don't generate brs nor bra
289<alkorr> so it will use several registers to be able to use jsr or jmp
290<Bagder> well, it should be possible to fix the gcc, even it its quite hard I figure
291<alkorr> i tried with static functions close to a function which calls those static functions
292<alkorr> without success
293<alkorr> well there several example like this which explains why I prefer not to use C for all
294<Bagder> for loops that is gonna make a difference, but for most code it is a penalty we can take, imho
295<alkorr> so you mustn't be surprised to see a lot of asm in my source
296<alkorr> i don't care for speed
297<alkorr> but for space
298<Bagder> you restrict the audience quite a lot by using asm, as not many people will be able to read it nor write it
299<wavey> low level functions can be asm
300<wavey> that's not a problem at all
301<alkorr> i'm speaking about low functions, not for your GUI :)
302<wavey> screen updating code can be a complex as you wan
303<wavey> because people will access it from C
304<alkorr> so we are okay
305<wavey> yup
306<Bagder> indeed
307<wavey> hoorah!
308* wavey chuckles
309* Bagder smiles
310<alkorr> it is not in my intention to do all the stuff in asm
311<Bagder> what parts are gonna start (have you started) with?
312<alkorr> LCD
313<alkorr> USB
314<alkorr> let me see my source
315<alkorr> timer
316<alkorr> lcd+backlight+led
317<alkorr> where i'm using atomic operation to set or clear port A and B
318<alkorr> so asm+c
319<alkorr> a start of ATA
320<alkorr> but i lost the main part in a harddisk crash
321<alkorr> ata is C
322<Bagder> what kind of lcd code do you have?
323<alkorr> for JBP
324<alkorr> i send you my source
325<Bagder> please do
326<Bagder> mail me at daniel@haxx.se
327<Bagder> my usb2 card has arrived!
328<alkorr> i don't send all my package
329<Bagder> I'm mainly interested in the lcd parts sright now
330<alkorr> just LCD parts and headers you could need
331<Bagder> right, thanks
332<alkorr> for JBR i don't try because i lose my JBR
333<alkorr> so i cannot try it
334<Bagder> I already have working code for the recorder
335<Bagder> I'll make a little api for the player built on your code
336<Bagder> did anyone make a table of all the available letters/characters on the player's LCD screen?
337<Zagor> yes
338<wavey> it's on the notes page next to the recorders
339<Zagor> it's not the recorder's, it's the player versions
340<Zagor> the new and old have different charsets
341<alkorr> there is difference between old and new text-lcd in JBP
342<alkorr> i have the new one which is quite compliant with ascii table
343<Bagder> aha, it could be clarified on the web page...
344<alkorr> by the way i'm not sure about my tables :)
345<alkorr> i never test them thoroughly
346<wavey> test?
347<wavey> what is that? ;)
348<alkorr> and even worse for old lcd since i don't have one
349<Bagder> btw, how do we read/fetch input from the keys currently?
350<alkorr> in lcd.c there is two tables for characters translations
351<alkorr> so our api can work with new and old taxt-lcd without changing our strings to display
352<alkorr> for the moment i use a polling method
353<alkorr> in fact it is the only way
354<alkorr> i'm speaking about JBP (player)
355<Bagder> fine enough, I would just like a defined api on how to do it
356<alkorr> in the original firmware, they use the interrupt itu0 for polling keys
357<alkorr> for JBR, it is much more complicated
358<alkorr> i explain
359<alkorr> you have two pins for two groups of fours keys
360<alkorr> those two pins are analogic
361<alkorr> so you need to scan periodically their pins and translate their value to determine which key is pressed or released
362<alkorr> a way it is to use the interrupt ADC in scan mode which gives us the value and will translate them in a more practical bitmap or somethig like it
363<alkorr> another way is to use the dma to scan those pins and generate the interrupt dei to translate
364<Bagder> I don't think you understand what I want ;-)
365<alkorr> ok you want for player or for recorder
366<alkorr> ?
367<Bagder> both preferably, but one at a time is fine too
368<alkorr> i just have for player
369<alkorr> ok
370<alkorr> as you can see it isn't a generic API for keyboard
371<alkorr> but you know where to poll them
372<Bagder> is there anything that prevents us from creating a "generic" api for this?
373<alkorr> no of course
374<alkorr> i was doing that in key.c but it is not my priority in fact
375<alkorr> so we are free to do so
376<alkorr> if you need info i can help you to do so
377<Bagder> because since I want to "simulate" this on X11, it gets easier if I can simulate the API
378<alkorr> yes but we need first to know what we need
379<alkorr> and quite now I'm still unsure about it
380<alkorr> so I don't have a clear API for keyboard
381<Bagder> yes, that sounds logical ;-)
382<alkorr> keyboard event to handle for exapmle ?
383<alkorr> are you using events ?
384<Bagder> x11 events?
385<alkorr> you know like in X or Windows or in TurboVision (if you knew that ;)
386<Bagder> yes, this is x11 it uses events
387<alkorr> something which can represent input or output event to handle by several entities
388<alkorr> i'm speaking about our final rockbox
389<Bagder> I'm not ;-)
390<alkorr> if you want an API
391<Bagder> I only want a simple input api
392<alkorr> to simulate
393<Bagder> it could be changed or improved later on
394<alkorr> well there is two possibilities
395<alkorr> using keybitmap
396<alkorr> or using key buffer
397<alkorr> to use a key buffer
398<alkorr> can you send me your file so i can see the way to handle UI ?
399<Bagder> its in CVS, there are many files
400<Bagder> its really simple: lcd_update() updates the screen
401<alkorr> oh that's true ??? ok i go and download them
402<Bagder> lcd_string() outputs a string
403<Bagder> lcd_position() sets the "cursor"
404<Bagder> so far
405<alkorr> direct actions on lcd ?
406<alkorr> or using buffer ?
407<Bagder> no, they manipulate the buffer and lcd_update() writes to the lcd
408<alkorr> so why lcd_update, ok
409<Bagder> but for the player I can't see any point in keeping a buffer
410<alkorr> by the way, isn't it Linus which has started something about fat32 ?
411<alkorr> i lost 3/4 of my works on it and i'm very down to redo all
412<Bagder> the web page says Alan, is that you? ;-)
413<Zagor> yes, he has some code for it
414<alkorr> yes but i did have a crash which causes loss of files which are exceeding 4 KB
415<Zagor> ok. we'll reassign that for linus
416<alkorr> in fact my fat32 was tighly coupled with ata
417<Zagor> so what should I put efter your name, alan? :)
418<Bagder> Zagor: you could modify my "planning" to "partly working"
419<Zagor> ok
420<alkorr> name of your mudule, Badger ?
421<Bagder> uisimulator
422<alkorr> well i would like to be able to use my serial as i could do before the crash
423<alkorr> it would be more easier to test my ATA
424<alkorr> if Linus can pass me his source i can adapt or modify it to use ATA
425<Zagor> i'll tell him
426<Bagder> we want Linus's source in CVS too
427<Zagor> yes
428<alkorr> it would speed my work instead of redoing all
429<alkorr> ok got it (uisimulator)
430<alkorr> cool your headers ;)
431<Bagder> it just does one lcd_string() and then it does lcd_update() and it shows the string
432<Bagder> hehe, thanks to figlet really
433<Zagor> the figlet man :-)
434--> linus (~linus@labb.contactor.se) has joined #rockbox
435<alkorr> be aware with shift operation
436<Bagder> lcd-recorder.c is the recorder-versions, lcd-x11.c is X stuff and lcd.c is generic
437<linus> Hi folks
438<alkorr> hi linus
439<alkorr> ok
440<Bagder> hey ho Linus
441<linus> I'll dig up my FAT32 source as soon as I get home
442<alkorr> you don't plan to have a buffer greater than screen for having vertical or horizontal scrolling on screen ?
443* Zagor wants Boulder Dash 8*D
444<Bagder> blah, I "plan" all sorts of things, this is not the final complete code
445* linus wants Tetris
446<linus> and Breakout
447<Bagder> this is for setting an api to play with
448<Bagder> increasing the buffer is a piece of cake should we want that
449<alkorr> well, I2C RTC is quite slow
450<alkorr> oh soory
451<alkorr> oh sorry, forget what i said
452<alkorr> there is no connection with lcd
453<alkorr> :)
454<Bagder> Gary said he got about 20frames/sec writing fullscreen, that's not too slow I'd say
455<alkorr> ok
456<alkorr> i just want to be sure there is nothing else which can reduce time
457<alkorr> my lcd was written to have the less time between two bits sent
458<alkorr> we cannot do it better
459<alkorr> (zagor) maybe MAS I2C can be slower in JBR than in JBP because of I2C RTC
460<Zagor> maybe
461<Bagder> linus: you should bring your gdb efforts to the CVS archive, alkorr wants 'em ;-)
462<Zagor> i have some new pictures and shematics for the serial cable. coming up in a minute
463<alkorr> well so long as i don't know why my serial doesn't work any longer it wouldn't be helpful
464<alkorr> i prefer to send my binary to a person who has a JBP and a working serial to tell me if it works
465<linus> I have a working serial
466<alkorr> any volunteer ?
467<Zagor> well my serial port is toast, unfortunately :-(
468<linus> ...but the rest of the archos is fried at the moment...
469<alkorr> beuuuuuuh :,((((
470<linus> ...but i can use my CPU board in Björns player. That works.
471<alkorr> oh good
472<linus> I will put the final touch on the stub on my trip to France next week. I'll keep you posted.
473<alkorr> okay i will prepare a simple binary which only communicate with serial line (no ata stuff or something which could lead to damage)
474<Zagor> uit
475<-- Zagor has quit ("Leaving")
476<linus> Hehe. I appreciate that...
477--> Zagor (~bjst@labb.contactor.se) has joined #rockbox
478<linus> Alan, is your serial port damaged or what?
479<alkorr> i want to be sure if it is my serial converter or my software which in pains
480<linus> Aaah.
481<alkorr> it is what i want to know
482<alkorr> it worked
483<alkorr> ok let me prepare the binary
484<wavey> hey linus
485<wavey> nice to meet you
486<linus> yo!
487<alkorr> okay
488<alkorr> to whom must i send the binary ?
489<Zagor> send it to linus@haxx.se
490<alkorr> ok but wait, it looks as if my strings are corrupted... it may be the reason
491<Zagor> ok
492<alkorr> anyway i suppose you won't be able to do so now
493<alkorr> no i can see on my lcd the string :/
494<alkorr> but my terminal doesn't display my string but some "@" can appear sometimes, any clues ?
495<Bagder> nope
496<alkorr> linus, i send you the first version by dcc send
497<alkorr> sorry, Badger you cannot dcc get my files ?
498<Zagor> now the rs232 converter is up on the mods page
499<Zagor> drawings and the whole shebang
500<alkorr> linus and badger : can you dcc get my files ? i should cancel those for Badger
501<Zagor> linus is away right now
502<Bagder> hm, I think I can receive dcc
503<alkorr> so i retry
504<alkorr> 8 files
505<Bagder> I've never received files using xchat before, but nothing seems to happen
506<Zagor> have you clicked "accept" or something?
507<Zagor> i think you need to mark it and accept it
508<Bagder> that's "auto accept" and I thought I'd get a question if I don't auto-accept
509<Bagder> absolutely nothing happens
510<Zagor> odd
511<alkorr> try : /dcc get alkorr
512<Bagder> that won't work due to my firewall
513<alkorr> i retry file by file
514<alkorr> instead of sending all file in one time
515<alkorr> oh okay
516<alkorr> oh yes the firewall
517<Bagder> but still, the announcement of the dcc is done using ctcp and that is plain irc so my client should still say something
518<alkorr> well i can send to zagor but not receive from zagor, seems to be a similar problem but the main difference is i'm using mIRC on Windows
519<alkorr> Badger : for key.h, macros cannot be used with variable as parameter -> key_pressed (ON) OK but key_pressed (key) ERROR
520<alkorr> there are just for commodity in developping
521<alkorr> i also lost my memory.c which handled a block or bytes allocation (using a similar slab techniques for blocks and bytes allocation in a block)
522<wavey> losing your memory.c is a sign of old age
523<wavey> or too much weed
524<Bagder> lcd_string() bugs :-/
525<linus> Alan, what is supposed to happen when running the program?
526<Zagor> bagder: alans files are at bjorn.haxx.se/rockbox/jox/
527<Zagor> go fetch :-)
528<alkorr> oh sorry
529<alkorr> ok
530<alkorr> well, it displays on the lcd :
531<alkorr> <<< JBP >>>
532<alkorr> and
533<linus> No it doesn't
534<alkorr> OK WORKING!
535<Zagor> haha
536<alkorr> what do you get ?
537<linus> It hangs without displaying enything
538<alkorr> i repeat what you must have is :
539<alkorr> "<<< JBP >>>"
540<alkorr> "OK WORKING!"
541<alkorr> don't plug you serial at boot
542<Zagor> i'm going, guys. see you later.
543<alkorr> it doesn't work at this moment, firmware doesn't clean very well
544<-- Zagor has quit ("Leaving")
545<alkorr> if it doesn't work yet
546<linus> all I can see it the "JUKEBOX 6GB bla bla..." and then it hangs
547<alkorr> hummm...
548<linus> *** back soon ***
549<alkorr> oh where do you plug your serail ? on the line-in ?
550<alkorr> try to send '0' or '1' to turn on or off backlight
551<linus> I have tried that. Nothing happens.
552<alkorr> if not, interrupts are ignored and so it got an error (overrun, frame or parity error)
553<alkorr> can you dcc get ?
554<alkorr> oh by the way did you scramble the bnary ?
555<linus> Havenb't tried. Shoot!
556<alkorr> you must do it
557<linus> I have a tip. Shut off all timer nterrupts: TIERo = 0, TIER1 = 0, etc.
558<linus> I didn't scramble it. That must be it. Hang on!
559<alkorr> there is not interrupt for sending jsut a polling
560<alkorr> but for receiving there is an interrupt (is that way i can turn on or off backlight when receiving '0' or '1')
561<linus> ...still dead, even after scrambling
562<alkorr> no lcd displaying ?
563<linus> Nope
564<linus> FYI, I have firmware 3.18
565<linus> Try to blink the red LED in the polling loop
566<alkorr> hummm, let me create a source package so you can modify and compile it...
567<linus> Great!
568<alkorr> can you dcc get ?
569<alkorr> linus ?
570<linus> Yup. Gimme da filez
571<alkorr> trouble ?
572<linus> "No file offered in SEND mode by alkorr"
573<linus> Alan?
574<linus> Alan: what is the name of the file?
575<alkorr> yes
576<alkorr> backup.tgz
577<alkorr> and now ?
578<alkorr> ok i was trying to send to Zagor :)
579<linus> :-)
580<alkorr> i move the sit() (enable interrupts) just after sending "Ok WORKING!"
581<alkorr> oops, sti ()
582<alkorr> tabs = 2 spaces
583<linus> Alan, I have to go now. I will look into your stuff ASAP. CU!
584<alkorr> ok i must also to go :)
585<-- linus has quit ("Leaving")
586<alkorr> bye all !
587<-- alkorr has quit ()
588<Bagder> lcd_string() works again, time to stop for today
589<-- wavey (~wavey@dlan1431.dircon.co.uk) has left #rockbox
590**** ENDING LOGGING AT Tue Mar 26 16:43:52 2002
591