--- Log for 16.07.105 Server: kornbluth.freenode.net Channel: #rockbox --- Nick: logbot_ Version: Dancer V4.16 Started: 4 days and 14 hours ago 00.00.08 # need to go now.. my girlfriend is coming.. will be back in about an hour 00.00.13 # austriancoder: to make a firmware for the original firmware to like, we use the descramble, mkboot chain 00.00.30 Nick austriancoder is now known as ac_away (~austrianc@80.120.117.30) 00.00.42 # hm, and scramble too in fact 00.00.43 # hehe 00.00.46 # how confusing 00.00.58 # found the it... http://www.rockbox.org/twiki/bin/view/Main/IriverBoot ;) There is the way to make it by hand 00.01.11 # ac_away: yes, but that makes a original firmware image 00.01.19 # that is only made to make a bootloader image 00.01.25 # not an ordinary rockbox image 00.01.38 Join muesli__ [0] (muesli_tv@Bc12c.b.pppool.de) 00.01.55 # memmem: maybe you could try to code a mkboot-clone for iaudio 00.02.24 # Bagder: Merge the firmware and the boot loader into a new firmware file - that is what i looked at the wiki page 00.02.25 # First I have to research how the bootloader will look like. 00.02.31 # Meh, this also stuff simply doesn't work 00.02.36 # *alsa 00.02.51 # see you all later - i hope 00.02.52 # ac_away: yes, that's done to make an image that flashes the bootloader 00.03.18 # memmem: how will you start the bootloader if you don't have the reset vector to patch? 00.04.57 # Badger: It seems to be two-staged. I'm waiting for austriancoder to get the BDM and send me the lower 64 KByte of the flash. Apparently, the firmware file starts at 0x10000, which seems also to be the entry point called by some code in the lower 64 KByte. 00.05.00 # amiconn: this is actually the OSS way, not alsa if I've understood things right 00.05.19 # I have a dev/dsp, but it doesn't play anything 00.05.28 Quit Harpy (Read error: 110 (Connection timed out)) 00.05.28 # xmms also hangs if I try to play sth 00.08.08 # how annoying 00.08.41 # Yes... as much as I like the linux idea, I still prefer windows 00.09.05 # I did not yet find a single box where I could get all hardware to work under linux 00.09.17 # well, possibly the same approach is easy enough to make work on Windows too 00.09.32 # amiconn: you create your box from the start with hw you know works ;-) 00.09.49 # Haha, how do I do this with a laptop? 00.10.01 # there are lists 00.10.05 # and info available 00.10.29 # I mean, for models that work fine 00.10.44 # Yes, but perhaps these models don' 00.10.50 # t fit my requirements? 00.10.57 # perhaps 00.11.25 Quit Lear ("Chatzilla 0.9.68.5 [Firefox 1.0.5/20050715]") 00.11.29 # I don't understand why this is so, but I think a linux workstation is as simple to use as a windows workstation for an average user... 00.11.46 Quit muesli- (Read error: 60 (Operation timed out)) 00.12.16 # ...but configuring linux properly so that everything works is extremely time consuming or even impossible with linux, even for a knowledgeable person 00.12.42 # yes 00.12.51 # but to me, there just is no other way 00.14.27 # I prefer to work with the PC, not for the PC... 00.14.35 # me too 00.14.50 # with Windows, Windows gets in the way 00.15.11 # For old windows, like 9x or even NT, you may be right 00.15.19 # Win XP just runs... 00.15.28 # it doesn't matter which to me, they're all the same 00.15.32 # just more icons lately 00.17.49 # What version of GCC is to be used for compiling rockbox for ColdFire? 2.95? 3.x? 00.17.51 # I dare to say Win XP runs about as stable as a current linux 00.18.06 # amiconn: that's not my experience at all 00.18.18 # memmem: 3.3.x or 3.4.x all work 00.18.45 # ...i dare to say that it hasn't really been a question of stability for years now, more like question of user interface and available tools to me 00.18.48 # I've never seen WinXP crash except in the rare case when there are very buggy hardware drivers 00.19.00 # it doesn't really crash, but things stop to work 00.19.05 # (but I think such an issue might crash linux as well) 00.19.06 # only to come back after a reboot 00.19.07 # What's the target specification? m68k-elf? 00.19.39 Quit muesli__ (Read error: 60 (Operation timed out)) 00.19.40 # memmem: http://www.rockbox.org/twiki/bin/view/Main/WebHome?topic=CrossCompiler 00.19.53 # Bagder: As I said, I don't like MS that much, and I would use Linux if it would take a reasonable amount of work to get it all running 00.20.09 # amiconn: hmm... my windows xp reboots every now and then, and it has several memory leaks, i haven't gotten it to run over a week without a reboot yet 00.20.15 # ...but that never worked for me in numerous tries, during several years 00.20.15 # but yea 00.20.19 # ever try one of the simple Debian-based distros? 00.20.20 # its the most stable windows yet 00.20.30 # Thanks! I followed the toolchain link, but that wasn't exactly helpful. 00.21.07 # Stryke`: I tried numerous SuSE's (way back in the low versions. The first had a kernel < 1.0) 00.21.19 # ...and debian itself, recently 00.21.48 # i've installed Ubuntu on a sister's computer, she had little troubles 00.21.49 # debian itself isn't a simple debian-based distro :) 00.22.08 # The majority of hardware works, but there are always those few but important things that don't work, and I can google as much as I want, I don't find the solution... 00.23.19 # ...like (in the past) AVM BlueFritz. Now we don't have that anymore, but I don't get WLAN to work... 00.23.41 # ...and I have no idea how to make ALSA work on my VM... 00.24.22 # ALSA is a serious pain in the ass, but once configured (with properly working dmix plugin), it's really good 00.24.40 # i hear that the configuring part has gotten significantly easier with newest versions 00.24.42 # The *once configured* being the big red key here! 00.24.59 # configuring i mean involves adding stuff to ~/.asoundrc 00.25.02 # Old problems, *now* solved: Nvidia 3d graphics, nvidia network card.... 00.25.37 # of course Linux will remain having driver problems compared to Windows 00.25.39 # for a very long time 00.26.01 # Not necessarily... it all depends on vendor support 00.26.03 # since most drivers to Linux don't come from the manufactorers, as the win versions do 00.26.19 # yes but vendors will continue to not care for a good while longer 00.26.31 # my prediction 00.26.35 # For instance, the WLAN chipset of the problematic wlan card is supported by the chipset manufacturer in linux... yet I can't get it to work 00.26.48 # i (having been a linux user for about 6 years now) have always had more problems with windows than with linux 00.26.51 # Well, for my DSL modem, the Linux driver works much better than the Windows driver. 00.26.57 # I compiled the driver, without problem, it loads and finds the card... 00.27.11 # ...but I can't get the darn thing to connect to the AP. No way... 00.27.27 # In windows it is 2 clicks and it is working 00.27.36 # when buying new hardware, i've always bought stuff known to work... and when you buy stuff known to work, it also works in linux straight away, not like after installing thousands of drivers and tools like in windows 00.27.41 # Linux problems I can fix, Windows problems tend to become huge and impossible to track 00.28.13 # * Bagder considers sleep 00.28.22 # crwl: If you have older hardware (= know to work) it is very likely supported in windows out of the box 00.28.35 # adding volume support to the x11 sim was a bit more work than I thought 00.28.59 # Bagder: I made the opposite experience. 00.29.11 # amiconn, well, i didn't say older hardware, just hardware known to work without needing to install all sorts drivers from third parties, like sound or network or TV tuner cards... 00.29.28 # i don't think my USB 2 controller still works at windoze 00.29.39 # but that doesn't matter, because i only need my gamepad and FF wheel there :-) 00.29.46 # I guess it is partly a state of mind 00.29.54 # I just can't use windows 00.29.59 # I have to fix my linux problems 00.30.05 # Bagder: I don't think so 00.30.25 # I don't need windows for gaming, because I don't do gaming at all 00.30.28 # I'm in the corner, I either fix my linux problems or I go nuts 00.30.37 # I can use both, they're not very different 00.30.53 # ...but the huge difference is support 00.31.03 # support? 00.31.10 # you ever get support for windows? 00.31.20 # For windows, there is microsoft support, for linux, you have to be lucky 00.31.23 # Bagder: Yes. 00.31.24 # you mean from vendors? 00.31.37 # There is support.microsoft.com, which is very helpful 00.31.42 # I don't know a single person who ever contacted microsoft 00.31.46 # I did 00.31.51 # now I do ;-) 00.31.51 # ...at work 00.31.57 # _at work_ yes 00.32.15 # Theere must be a reason why our company runs about 2 dozen windows servers, but opnly one windows box 00.32.22 # you can buy support for linux too 00.32.26 # erm, one linux box 00.32.44 # a reason yes, but not against linux per se 00.32.59 # Even one of my colleagues who administered real unix systems before... 00.33.00 # our company runs most servers on linux 00.33.02 # If I ever write code for rockbox: how do I get write access for CVS? 00.33.19 # ...says that many things are just done faster and easier in windows 00.33.32 # memmem: the normal procedure is that you send in a few patches first 00.33.37 # OK. 00.34.34 # memmem: and when we see that you are a swell and good guy, we hand you the golden password and you're in 00.35.25 # No paperwork à la FSF? 00.35.30 # nope 00.35.53 # you don't sign over your copyright either 00.36.44 # and of course, we'll expect you to be subcribed to the mailing list by then at least 00.37.30 # I do not yet know how much I want to commit to working on rockbox; I already have three sourceforge projects. 00.37.40 # only three? ;-] 00.37.42 # ...one of which being dead. 00.37.54 # let me count mine... 00.38.11 # 12 00.38.23 # I'm the sole developer on my SF projects. 00.38.42 # and several of my projects are not on sf 00.38.52 # hehe 00.38.59 # Pissing contest? ;-) 00.39.03 # indeed 00.39.29 # OK, I think I wrote about 2e6 LOC. 00.39.46 # memmem: still, we'll appreciate your contributions no matter how small they are 00.40.10 # 2 million lines? 00.40.15 # in three projects? 00.40.35 # No, all projects (commercial etc.) of my lifetime, as estimated about 10 years ago. 00.42.40 # wc -l ? ;-) 00.54.04 # The NoDo doc says that recording WAV won't be implemented as "the recording hardware (MAS) does not allow us to do this." I think that's not true for ColdFire-based devices. 01.02.13 Join Maxime [0] (~flemmard@fbx.flemmard.net) 01.02.40 Join jpegreen [0] (~Jeremy@234-64-212-66.spl.org) 01.05.23 # re 01.05.28 Nick ac_away is now known as austriancoder (~austrianc@80.120.117.30) 01.06.48 # memmem: any research news? 01.07.27 # No. Setting up the tool chain. GCC 3.3.5 cannot compile rockbox, internal compiler error. 01.07.41 # ah ok... 01.07.51 # i will check now some more chips on the board 01.07.58 # Great! 01.08.10 # I like those M3 scans... 01.08.45 *** Saving seen data "./dancer.seen" 01.08.49 # i will also scan more stuff this night 01.10.59 # memmem: have you an m3? 01.11.13 # X5L 30 GB. 01.11.45 # ah: audio chip: AIC23B 54T C1C7 -> same as M3 01.12.19 Quit Moos (Read error: 110 (Connection timed out)) 01.14.59 # Does any body know which file in the source code that I would need to modify the %pf settings for the .wps file types to create my own design? 01.20.38 Quit HCl ("Lost terminal") 01.21.11 Join hcl [0] (hcl@titania.student.utwente.nl) 01.21.17 Nick hcl is now known as HCl (hcl@titania.student.utwente.nl) 01.28.24 Quit CBM-away (Read error: 113 (No route to host)) 01.35.36 Quit Stryke` ("Friends don't let friends listen to Anti-Flag") 01.55.03 Join MrStaticVoid [0] (~jlee@69-175-94-207.frdrmd.adelphia.net) 02.01.40 Join ac_scanner [0] (~5078751e@labb.contactor.se) 02.11.48 # The internal scan frequency of the iriver lcd is indeed ~70 Hz (in greyscale mode). Sounds familiar. 02.13.26 # amiconn: what do you think, how long will it take to get the color api up? 02.14.30 # There are a lot of unknown variables... but I think once we know the lcd controller, it shouldn't take long 02.15.03 # I'm still thinking about getting a H3x0... maybe I should just do it 02.15.17 # i think i have found the lcd controller of the iaudio x5 02.15.33 # Would be my 5th rock-box though... 02.17.21 # if i give you an image can yu help me to identify it? 02.17.55 # I could try. Just put the image(s) in the wiki 02.18.16 # http://www.rockbox.org/twiki/pub/Main/IaudioX5HardwareComponents/lcd.jpg 02.19.36 # oh, iaudiox5 is there as a new target for rb? 02.20.33 # yep 02.20.43 Quit memmem ("ERC Version 5.0.3 $Revision: 1.726.2.17 $ (IRC client for Emacs)") 02.23.26 # ac_scanner: Hmm. This is the whole lcd module, not the controller. 02.23.46 # Seems to use the same type of marking as the H3x0 lcd 02.23.59 # cf http://www.rockbox.org/twiki/bin/view/Main/IriverH3XXHardwareComponents#LCD_Display 02.24.32 # H3x0: COG-IZ12049 X5: COG-IZ12066 02.24.52 # hmm 02.24.52 # COG just means "chip on glass", so that doesn't say much 02.25.10 # if i had success to an broken iaudio 02.25.34 # maybe we can find here more: http://www.varitronix.com/index_ie.php 02.25.52 # anybody know if there is a way to use iTunes to sync with your Archos Jukebox series? 02.28.30 Join ashridah [0] (ashridah@220-253-123-147.VIC.netspace.net.au) 02.33.00 Join asdsd____ [0] (~asdsd@h-67-100-30-142.miatflad.dynamic.covad.net) 02.33.04 Part asdsd____ 02.37.57 Part jpegreen 02.43.51 # i mailed vle... maybe we get some informations 02.44.08 # ac_scanner: The logo (left of the 'QC pass' text) looks the same for H3x0 and X5 lcd 02.44.16 # ...but it's rather blurry 02.44.55 # lets hope, that they use very similar controlers 02.45.09 # i am afraind to open the lcd module.. 02.45.25 # What's the resolution of the X5 lcd? 02.46.07 # 160x128 02.50.30 # I would really like to see that logo without blur. 02.50.47 # It seems to be the only hint towards the (module) manufacturer 02.50.54 # i could try it 02.51.03 # photoshop could help here 02.51.07 # ...and that should help to find the controller manufacturer 02.51.25 # I already opened it in Photoshop (elements) 02.51.34 # i think that blurry logo is the VL logo 02.51.44 # but i can rescan it with about 2100 dbi 02.53.17 # i have mailed vl already 02.53.38 # "VL Electronics, member of varitronix international group" 02.53.45 # jep 02.53.53 # see my link abouve 02.54.22 # http://www.varitronix.com/index_ie.php 02.58.14 # it is VL or VB 02.58.17 # on the logo 03.00.13 # The L might look like a B (or 8), because the logo shows the L in a 7-segment-like style 03.00.52 # ok.. so it is VL 03.01.05 # like printed on the module 03.01.38 # has anyone found full specifications for the lcd yet? 03.03.36 # not yet ;( 03.04.09 # i assume that's what you requested in the email then 03.04.35 # jep.. i asked if there is a public datasheet 03.08.14 # * ac_scanner will go now to bed 03.08.35 Quit ashridah ("Leaving") 03.08.46 *** Saving seen data "./dancer.seen" 03.10.31 Join CBM-away [0] (~youshould@tc2-225-085.altelco.net) 03.11.21 Quit ac_scanner ("CGI:IRC (EOF)") 03.16.23 # back g 03.16.23 # http://www.hitachi-displays.com/en/catalog/cellular_phones/2016427_18537.html 03.17.42 # Hmm, I'm on to something as well 03.18.17 # It seems Varitronix (sometimes) works together with IZ Display, a Korean company 03.18.28 # oooh 03.18.38 # The Numbers start with IZ, and both iriver and cowon are korean too... 03.19.11 # so IZ Display could be the module company? 03.19.53 # Either way. 03.20.17 # There may be 3 manufacturers involved; panel, controller, and module. 03.20.38 # and we know 2 of them 03.22.49 # http://www.iztek.co.kr/ 03.24.12 # its not a very useful site 03.24.20 # hard to read 03.27.39 # i think and hope that Varitronix can help us 03.29.00 # now it is realy time to sleep 03.29.28 Part austriancoder 03.35.52 Quit Sucka ("a bird in the bush is worth two in your house") 03.36.10 Quit hicks (Remote closed the connection) 03.37.01 Nick CBM-away is now known as CheeseBurgerMan (~youshould@tc2-225-085.altelco.net) 03.41.05 Join ashridah [0] (ashridah@220-253-121-58.VIC.netspace.net.au) 03.45.18 # * amiconn now has 7 shades of grey on his H1x0 lcd.... 03.45.46 # * CheeseBurgerMan has 262,000 colors on his H320. :P 03.46.13 # Haha, small wonder, that lcd supports 256K colors natively... 03.46.29 # ..but the H1x0 lcd only supports 4 shades natively... 03.46.39 # ...and I do have 7 now... 03.46.57 # ...it seems that I _can_ mix 4-grey mode and pixel flipping 03.47.46 # ....that might allow for up to 49 shades :) 03.48.19 # :) *CheeseBurgerMan snickers in the background as it's still very few compared to his... :P 04.04.41 Join StrathAFK [0] (~mike@dgvlwinas01pool0-a225.wi.tds.net) 04.05.59 Quit ashridah (Read error: 104 (Connection reset by peer)) 04.06.07 Join QT_ [0] (as@area51.users.madwifi) 04.07.48 Join ashridah [0] (ashridah@220-253-121-58.VIC.netspace.net.au) 04.09.20 Quit QT (Read error: 60 (Operation timed out)) 04.09.41 # 15 greyscales on the screen with my experimental plugin 04.10.09 # A bit flickery, but that's without random pattern shifting... 04.10.31 # wont it consume more precious processing power? ;) 04.10.51 # Yes it does, that's why the greyscale lib is for plugins only 04.11.00 Quit cYmen (Read error: 113 (No route to host)) 04.11.04 # ah, i see 04.22.17 Quit Strath (Read error: 110 (Connection timed out)) 04.40.44 Join eleom1 [0] (~da335148@labb.contactor.se) 04.41.04 Quit eleom1 (Client Quit) 05.04.29 Join amiconn_ [0] (~jens@p54BD4EAB.dip.t-dialin.net) 05.08.50 *** Saving seen data "./dancer.seen" 05.19.22 Quit xen` (Read error: 110 (Connection timed out)) 05.22.06 Quit amiconn (Read error: 110 (Connection timed out)) 05.22.06 Nick amiconn_ is now known as amiconn (~jens@p54BD4EAB.dip.t-dialin.net) 05.23.33 Join Hijacker [0] (~Hijacker@dsl-084-058-047-210.arcor-ip.net) 05.57.13 # hrm. 05.57.19 # i seem to have issues tying to play large ogg files 05.59.05 # or possibly just some oggs in general. :/ 06.06.51 Quit CheeseBurgerMan (Read error: 104 (Connection reset by peer)) 06.39.47 Join CheeseBurgerMan [0] (~youshould@tc2-225-085.altelco.net) 06.57.26 Quit Cassandra (Read error: 110 (Connection timed out)) 07.08.52 *** Saving seen data "./dancer.seen" 07.09.29 Nick CheeseBurgerMan is now known as CBM-away (~youshould@tc2-225-085.altelco.net) 07.52.11 Quit Hijacker (Read error: 104 (Connection reset by peer)) 09.08.53 *** Saving seen data "./dancer.seen" 10.09.52 Join Harpy [0] (Ju1x6utjl3@dsl-hkigw7wbb.dial.inet.fi) 10.25.23 Join pilled [0] (dearth@ip-130.net-82-216-140.issy4.rev.numericable.fr) 10.26.56 Quit pill (Read error: 110 (Connection timed out)) 10.26.57 Nick pilled is now known as pill (dearth@ip-130.net-82-216-140.issy4.rev.numericable.fr) 10.43.53 Nick QT_ is now known as QT (as@area51.users.madwifi) 10.52.27 Join cYmen [0] (~cymen@nat-ph3-wh.rz.uni-karlsruhe.de) 10.54.25 Join Klyr [0] (~klyr@evr91-1-82-227-13-45.fbx.proxad.net) 10.54.33 # hello 11.04.12 Join matsl [0] (~matsl@1-1-4-2a.mal.sth.bostream.se) 11.08.56 *** Saving seen data "./dancer.seen" 11.18.11 Quit matsl (Remote closed the connection) 11.37.24 Quit Maxime (Read error: 104 (Connection reset by peer)) 11.37.26 Join Maxime [0] (~flemmard@fbx.flemmard.net) 11.40.39 Join memmem [0] (~user@p54A205A8.dip0.t-ipconnect.de) 11.51.50 Join Lear [0] (~chatzilla@h143n1c1o285.bredband.skanova.com) 11.52.17 Join einhirn [0] (Miranda@carlsberg.heim2.tu-clausthal.de) 11.57.01 Quit memmem ("ERC Version 5.0.3 $Revision: 1.726.2.17 $ (IRC client for Emacs)") 12.11.32 Quit Rori () 12.11.37 Join austriancoder [0] (~5078751e@labb.contactor.se) 12.11.41 # morning 12.11.58 # amiconn: any news about lcd controller? 12.12.17 # morning 12.12.20 # No, sorry 12.13.43 Quit Bagder ("Off to search for that connect-resetting peer guy!") 12.14.33 # time to eat something 12.20.11 # Very good news for H1x0 owners: The grayscale library is definitely possible on that LCD, and even in 4-grey LCD mode 12.21.02 # That means, it will support overlay operation like on the archos (having a 'high-greyscale window' and displaying normal 4-grey contents around it), 12.21.14 # and it will support up to 49 shades of grey 12.21.30 # ...with only ~10% CPU load 12.22.18 # The only drawback is that it requires to boost the CPU to 120 MHz permanently (to avoid flicker due to CPU frequency changes, not due to performance problems) 12.23.02 # ...of course thsi boost will only happen while actually displaying a greyscale overlay 12.25.09 # Perhaps it will even support 97 shades... 12.31.15 Join memmem [0] (~user@p54A209B0.dip0.t-ipconnect.de) 12.32.31 # Hi ac & amiconn, the LCD controller has two 16-bit registered mapped into the ColdFire memory space: a control register at 0x20008000 and a data register at 0x20008002. The screen memory seems not to be mapped. 12.32.46 # (I'm talking about the iAUDIO X5.) 12.33.07 # The screen memory isn't mapped on any of the other lcd controllers 12.33.19 # LCD is controlled completely via i/o 12.33.43 # Sounds very familiar so far... 12.33.54 # I think it uses 4 bytes per pixel. 12.34.14 # 16 bit means iAudio either uses only 64K colours, or they use one of the weird 16+2 bit modes 12.34.37 # 4 bytes is 32 bits... 12.34.40 # ...meaning that using 4 bytes/pixel in memory wastes 14 bits per pixel 12.34.59 # In memory, 3 bytes per pixel are used, but that's an implementation detail. 12.35.42 # Here's a clue which might help in identifying the controller: When sending a command, it's shifted left by one bit. Ditto for the parameter. Sounds a bit unusual to me (who has no previous experience with LCD controllers). 12.35.55 # Yes, then it seems to work like the controllers I already read about 12.36.10 # Any datasheets? 12.36.54 # (16 +2 mode needs transferring 2 words per pixel, and using 3 bytes in memory only wastes 6 bit per pixel) 12.37.20 # Initialization seems to be complex, the firmware sends about 33 commands. 12.37.28 # http://www.epson-electronics.de/upload/PresidioIndustries/product/Semiconductors/LCDController-Driver/SingleChipTFTLCDDriver/S1D19105_TM_rev1_1.pdf 12.37.42 # This is the epson controller chip that might be the one in H3x0 12.38.02 # Thanks, I'll check the commands. 12.38.46 # All LCD controllers I've seen so far are very similar regarding controlling 12.39.46 # (archos recorder (solomon, b&w), player (another solomon, charcell), iriver (epson, 4-grey), iriver remote (tomato, b&w)) 12.40.30 # This one seems to require some time between certain commands, the firmware does sleeps of various lengths during LCD initialization. 12.41.13 Join hicks [0] (~hicks@zeus.mups.co.uk) 12.41.21 # That's common 12.41.40 # The H1x0 LCD does need that too 12.42.15 # Ugly. 12.42.39 # memmem: good news 12.42.49 # BDM? 12.43.06 # BTW, there's another flash memory region not contained in the firmware file... 12.43.18 # ping 12.43.29 # well that seems to work.. 12.43.30 # hi.. 12.43.44 # memmem: i mean.. good news that you found out some important stuff about the lcd 12.46.24 # memmem: This was the reason why some people experienced weird lcd effects on H1x0 especially in inverse mode, before the init sequence was fixed 12.46.43 # The init requires 100 ms pause in one place 12.46.43 Quit austriancoder ("CGI:IRC (EOF)") 12.46.57 Join austriancoder [0] (~5078751e@labb.contactor.se) 12.47.00 # re 12.50.10 # Hmm, that Epson controller seems to need the data shifted left by two bits in 16-bit mode. 12.51.23 # ...but who knows how the data bus is wired. 12.52.09 # It shifts the data itself, to get it expanded to 18 bits internally 12.52.35 # I already thought about the implementation of a H3x0 LCD driver, pretending the controller chip is an epson 12.53.20 # Actually it seems easier to implement the various graphics primitives in high colour than with bit-packed formats like b&w or 4-grey 12.54.15 # The Epson controller expects to get the data in bits 2 through 9, whereas the firmware shifts left by one bit only. 12.55.13 # (I'm talking about the commands and their parameters, not about pixel data.) 12.55.18 # The epson is actually a weird thing. It can operate in 8bit, 9bit, 16bit, full 18 bits, 16+2bit and 2+16 bits 12.55.35 # The command is always the upper 8 bits iirc 12.56.06 # 8bit and 16 bits mode only allow 64K colour, the other modes allow 256K colour 12.57.08 Join Asku [0] (~aksu@adsl-39.180-DynIP.ssp.fi) 12.57.10 # You'll probably need to find out how the data bus is hooked up to the lcd 12.57.35 # The specs claim that the X5 has 1<<18 colors, but the firmware might well use less colors. 12.57.46 # s/less/fewer/ 13.00.39 # The commmands sent by the firmware don't match the Epson commmands at all. Any other datasheets? 13.01.07 # no, sorry 13.01.32 # I think it's not the Epson controller. 13.04.54 # Hmm, do you know where the controller chip is located on the pcb? i think it should have some markings or manufacturer.. 13.05.55 # or is the display just directly connected to cpu? 13.06.17 # Usually the lcd controller chip is part of the module 13.06.30 # http://www.rockbox.org/twiki/pub/Main/IaudioX5HardwareComponents/lcd.jpg 13.06.44 # backside of the tft-lcd 13.06.49 # Ah.. then it should be possible to find out the manufacturer and directly ask from the manufacturer about that module 13.07.25 # nice, there are some markings at least 13.07.42 # Module manufacturer and lcd manufacturer (of both X5 and H3x0 lcd) are very likely Varitronix and IZ Display) 13.08.10 # Varitronix is located in Hong Kong, IZ Display is Korean 13.08.38 # for example i got specs for some hitachi graphics lcd in pdf form by emailing to them (those specs can't be found on net) 13.08.58 *** Saving seen data "./dancer.seen" 13.09.20 Join bumi [0] (~blabla@bzq-218-237-16.red.bezeqint.net) 13.09.28 # hey guys 13.09.35 # just came here to say Way To Go:D 13.09.36 # how long did you wait for an answer? 13.09.49 # 2 13.09.52 # :P 13.09.58 # austriancoder: Hmm, i think it was something over a week 13.10.39 # Any chance that the Hitachi is used by the X5? By looking at the datasheet I could tell... 13.11.08 # because i send Varitronix a mail... but maybe we should resend a serious mail and ask for both lcds 13.11.47 # yes, that might help. And if possible, try sending / faxing the message with a company name 13.12.21 # i dont own or work in a company 13.12.47 # Maybe Linus could do that... 13.12.52 # Hmm, somebody who works in a company should probably try that.. 13.15.01 # i think that linus is our man 13.16.12 Quit edx (Read error: 110 (Connection timed out)) 13.16.26 Join Moos [0] (DrMoos@m214.net81-66-158.noos.fr) 13.16.36 # Hi guys 13.18.08 # hi 13.18.53 Nick austriancoder is now known as ac_away (~5078751e@labb.contactor.se) 13.41.41 Join Febs [0] (~chatzilla@207-172-122-81.c3-0.rdl-ubr4.trpr-rdl.pa.cable.rcn.com) 13.42.12 Quit ac_away ("CGI:IRC") 13.44.54 Quit memmem ("ERC Version 5.0.3 $Revision: 1.726.2.17 $ (IRC client for Emacs)") 13.49.32 Join webguest80 [0] (~51429ed6@labb.contactor.se) 13.50.16 Quit webguest80 (Client Quit) 13.52.25 Join jamesshuang [0] (~james@24.149.176.92) 13.53.04 # hey everyone, just curious... is there any documentation for the internal rockbox bitmap format? 14.04.34 Quit thegeek (Read error: 110 (Connection timed out)) 14.06.00 Quit bumi (Read error: 110 (Connection timed out)) 14.20.08 Join R3nTiL [0] (~53456e8c@labb.contactor.se) 14.24.53 Join thegeek [0] (na@ti521110a080-0242.bb.online.no) 14.26.04 # slasheri: new dsp code commited. I'll stick around for a while in case there are problems... :) 14.35.10 Quit R3nTiL ("CGI:IRC (Ping timeout)") 14.51.05 # slasheri: hmmm... are track changes coming a bit early now? not sure yet, but... 14.55.48 Join edx [0] (edx@p54A8F533.dip.t-dialin.net) 14.57.00 Join Acksaw [0] (~5005a006@labb.contactor.se) 14.57.20 # Hey all 14.57.58 Join textchimp [0] (~chimp@ip67.net66.ipnetworks.net.au) 14.59.16 # my keyboard and mouse are both packing up 14.59.51 # had enough of the drunken beatings? :) 15.02.48 # more than likely 15.03.43 # so rockbox is working pretty nicely on the i120 15.04.01 # damnit. anyone feel like poking at an .ogg i've got that refuses to play in my iriver? 15.04.12 # AFAIK it works 15.04.18 # except that it hangs when it tries to turn itself off after the specified auto-off time....anyone else getting that? 15.04.21 # I hae a h320 so I wouldnt know =D 15.07.11 Quit jamesshuang (Read error: 110 (Connection timed out)) 15.08.13 Join Enjoyman [0] (~51429ed6@labb.contactor.se) 15.08.30 # hello folks :) 15.08.35 # ashridah: chained? :) 15.09.00 *** Saving seen data "./dancer.seen" 15.09.00 # hey Lear thanks for your DSP rework 15.09.20 # lear: i don't think so. 15.09.28 # other oggs from the same source work okay. 15.09.53 # i've got a little question for Slasheri/Lear the professionals of playback :) 15.10.12 # cant wait for new h300 rockbox fw (if they do make it) 15.10.28 # enjoyman: dsp.c is just a small part of the playback, so don't expect too much. :) 15.10.29 Quit Enjoyman (Client Quit) 15.10.31 # lear: give me a few, and i can upload one. 15.10.40 Join Enjoyman [0] (~51429ed6@labb.contactor.se) 15.11.08 # ashridah: Yeah, I could throw my ogg parser on it, and see what happens... 15.11.33 # Slasheri/Lear: i know it's "very easy" for you to add to playback the peak calculations, no? 15.11.51 # for the peak meater 15.12.23 # no? 15.13.11 # Lear, no? 15.14.47 # well, like i say, it'll take me a while, being on dialup and all 15.14.50 # Doesn't sound too difficult, no... Probably something for the firmware part though, and it would eat some CPU, no doubt about that. :) 15.16.56 # Lear: is it in your competences, to add this calculations, if ar'nt needed much time? 15.17.02 # :) 15.17.25 # well, I need to know what the peak meter needs before I can judge that. :) 15.18.00 # ok 15.18.56 # i assume guys like amiconn, Bagder... know this concept for the first Rockbox players 15.19.50 # peak meter is very usual :) 15.25.06 # Part 15.25.10 Part amiconn 15.27.16 # Lear: i don't find documentations for you about peak meter :( 15.27.48 # mas spec sheet says very little about it, but reading the peakmeter source gives some hints... 15.28.05 # true 15.28.49 # Lear: okay, give http://ashridah.customer.netspace.net.au/01.%20Midlife%20Crisis%20(Faith%20No%20More).ogg a poke 15.30.58 # Foobar says it all: three chained streams. Playback currently not possible... 15.33.09 Quit Acksaw ("CGI:IRC") 15.33.32 # odd. wonder why some streams from the same source are okay, and that one isn't. 15.33.42 # ah well 15.33.46 # Lear: I'm sure that if one of you 2 (with Slasheri) begin to look in the peak calculations, this way will be very easy for the other :) i hope in you :) 15.34.16 # but apear Slasheri don't be here :( 15.34.32 # for currently 16.03.56 Quit ashridah ("sleep") 16.06.34 # Hmm.. maybe i could look that peek thing soon.. :) 16.07.08 # Hi Slasheri :) 16.07.10 # Lear: nice! i will check that soon :) 16.07.12 # hi :) 16.07.27 # thanks for all 16.19.32 Quit Nibbler ("life is like a rental car, you fuck it up, and give it back.") 16.27.35 Join Nibbler [0] (~sven@port-212-202-193-100.dynamic.qsc.de) 16.36.56 Quit einhirn (Read error: 104 (Connection reset by peer)) 16.39.59 Join einhirn [0] (Miranda@carlsberg.heim2.tu-clausthal.de) 16.51.59 Join asdsd____ [0] (~asdsd@h-67-100-30-142.miatflad.dynamic.covad.net) 16.53.06 Part asdsd____ 17.00.59 Quit einhirn (Read error: 104 (Connection reset by peer)) 17.01.16 Join BBub_ [0] (belzebub16@dsl-084-059-232-087.arcor-ip.net) 17.01.17 Quit BBub (Read error: 104 (Connection reset by peer)) 17.01.19 Nick BBub_ is now known as BBub (belzebub16@dsl-084-059-232-087.arcor-ip.net) 17.03.14 Join einhirn [0] (Miranda@carlsberg.heim2.tu-clausthal.de) 17.03.17 Quit einhirn (Read error: 104 (Connection reset by peer)) 17.08.11 Join Sucka [0] (~NNSCRIPT@host81-156-157-175.range81-156.btcentralplus.com) 17.09.01 *** Saving seen data "./dancer.seen" 17.09.03 Join einhirn [0] (Miranda@carlsberg.heim2.tu-clausthal.de) 17.16.40 Quit einhirn (Read error: 104 (Connection reset by peer)) 17.21.06 Join einhirn [0] (Miranda@carlsberg.heim2.tu-clausthal.de) 17.24.10 Quit einhirn (Read error: 104 (Connection reset by peer)) 17.26.19 Join einhirn [0] (Miranda@carlsberg.heim2.tu-clausthal.de) 17.33.12 Quit einhirn (Read error: 104 (Connection reset by peer)) 17.34.23 Quit Enjoyman ("CGI:IRC") 17.35.31 Join einhirn [0] (Miranda@carlsberg.heim2.tu-clausthal.de) 17.38.07 Quit einhirn (Read error: 104 (Connection reset by peer)) 17.40.27 Join einhirn [0] (Miranda@carlsberg.heim2.tu-clausthal.de) 17.44.57 Join lodesi [0] (~moi@62.34.146.180) 17.52.20 Nick StrathAFK is now known as Strath (~mike@dgvlwinas01pool0-a225.wi.tds.net) 18.16.28 Join KasKaraK [0] (~KasKaraK@34.34.119-80.rev.gaoland.net) 18.16.39 # Hi 18.18.39 # I wanted to submit a little bug here as it is the way to do (wiki say "use the mailing list or irc" :) ) 18.18.53 # somebody interested ? 18.21.09 Join Stryke` [0] (~Chairman8@cpe-24-168-110-99.si.res.rr.com) 18.23.43 Quit lodesi ("Leaving") 18.32.00 Join lodesi [0] (~moi@62.34.146.180) 18.37.17 # what is it? 18.37.38 # it's about "space left on disk" as reported by the info menu 18.37.47 # maybe not a big bug 18.38.03 # i thes vorbisgain going to be supported in the rockbox? 18.38.06 # is the 18.39.37 # KasKaraK: you are right, its wrong 18.39.41 # Asku: no idea 18.40.08 # I have 89Mo left, and it say 8.9Go 18.40.13 # ok 18.40.42 # I wanted to open a bugtrack but wiki say not to do this with "development code" 18.42.57 Join XavierGr [0] (~XavierGr@ppp49-adsl-96.ath.forthnet.gr) 18.43.04 # Hello! 19.08.02 Quit Lear ("Chatzilla 0.9.68.5 [Firefox 1.0.5/20050715]") 19.09.05 *** Saving seen data "./dancer.seen" 19.11.40 # how can I print the compilation text to a file? I use the '>' operator but the errors are not included there 19.12.59 Join cYmen_ [0] (~cymen@nat-ph3-wh.rz.uni-karlsruhe.de) 19.13.44 Quit cYmen (Read error: 104 (Connection reset by peer)) 19.19.05 Quit Stryke` (Read error: 110 (Connection timed out)) 19.19.15 # XavierGr: replace your '>' by '2>&1>' 19.19.28 # if you're on linux :) 19.19.42 # lest see 19.20.48 # no didnt work, thanks anyway 19.21.04 # I use cygwin by the way 19.21.07 # so... 19.21.07 # make >file 2>&1 19.21.14 # hmm... 19.21.53 # thanks Slasheri that worked! 19.21.57 # good :) 19.23.35 # the "2" is output sterr, so what it does is that it redirects the errors into the standard output 19.24.08 # right Slasheri? 19.26.34 # I thought that the simple > is output to file 19.26.46 # it is 19.26.47 # I dont know all these 2 and &1 operators at all 19.26.58 # 1 is normal stdout 19.27.03 # 2 is sterr 19.27.06 # or something 19.27.12 # dont quite remember the names 19.27.16 # when you just do > 19.27.29 # you only redirect the "1" part of the programs output 19.30.33 # * XavierGr is linux ignorant :( 19.31.23 # well 19.31.26 # mmh..didn't knew slasheri's syntax :) 19.31.28 # I don't think most people know 19.31.34 # even those that know linux a bit 19.32.28 # thegeek you're right,but sterr=stderr 19.32.48 Quit textchimp (Read error: 110 (Connection timed out)) 19.33.35 # ah 19.33.36 # yes;) 19.33.41 # thegeek: yes 19.33.57 # 3 is stdin 19.34.17 # and & is required because 2>1 would just redirect error messages to a file named 1 19.34.33 # yes 19.34.55 # I have not used it much, only in a few shellscripts here and there 19.34.56 # ;) 19.36.37 Quit Strath ("Client closed") 19.37.24 # implicit declaration of function `remote_tree_init' does this means that I have not declared the function? 19.38.11 # yep, or included it in a define 19.38.23 # but if linker fails too, it really is undeclared 19.38.46 # I get a warning 19.38.59 # and the simulator dont work as expected 19.39.05 # I will try to remove the warnings 19.39.17 # if everything builds ok, despite the warning, then the declaration is missing from a header file 19.39.26 # why isnt there a main.h file 19.39.29 # ? 19.39.35 # there should not be 19.39.43 # you have to create your own header file 19.39.59 # something like remote-tree.h (if your source is remote-tree.c) 19.40.10 # yes I got it 19.40.29 # and #include 'remote-tree.h' from main.c right? 19.40.37 # and then you will include that remote-tree.h everywhere you call that function 19.40.42 # (including remote-tree.c) 19.40.52 # yes, but " instead of ' 19.40.58 # including the .c too? 19.41.03 # yep 19.42.02 # (i mean that you should #include "remote-tree.h" in the remote-tree.c too, not the .c file itself ;) 19.42.31 # ah ok because I got a bit confused there 19.44.46 # how can I reproduce the warnings? Because after 1 compilation which it gave me all the warnings now every time I 'make' I dont get them. Is this expected? Maybe I will change a file a bit and resave it. 19.45.07 # yes the last did the work 19.45.48 # touch remote-tree.c 19.49.20 Join KasKaraK_ [0] (~KasKaraK@34.34.119-80.rev.gaoland.net) 19.52.25 Join solex [0] (~jrschulz@d001160.adsl.hansenet.de) 19.54.00 # strange! 19.55.59 # I have declared the function remote_tree_init in remote-tree.c (included the remote-tree.h where I declare the dunction) and in the main.c where I call remote_tree_init (included the remote-tree.h) I get the same implicit error! 19.57.52 Quit KasKaraK (Read error: 60 (Operation timed out)) 20.01.30 # what you have in remote-tree.h? 20.03.57 Quit solex_ (Read error: 110 (Connection timed out)) 20.06.55 # the exact content of tree.h but with changed function names to refer into the remote-tree.c (which is the same with tree.c with changed function names to refer to the remote) 20.07.24 # the problem might be multiple references of functions or variables. I will do it again another time 20.07.30 # Hmm.. you should have the remote_tree_init there 20.07.51 # well I have declared it in remote-tree.h 20.08.14 # and in the beginning #ifndef _REMOTE_TREE, #define _REMOTE_TREE ... 20.09.06 # do you think that tree.c must include remote-tree.h or is it irrelevant? 20.10.35 # well...no time for that today I will try again tomorrow. I am dying for proper remote support!! 20.17.38 Quit thegeek (Read error: 104 (Connection reset by peer)) 20.18.21 Join thegeek [0] (na@ti521110a080-0242.bb.online.no) 20.26.05 Quit XavierGr () 20.27.45 Join Lear [0] (~chatzilla@h143n1c1o285.bredband.skanova.com) 20.28.24 Nick CBM-away is now known as CheeseBurgerMan (~youshould@tc2-225-085.altelco.net) 20.42.07 Quit Lear ("Chatzilla 0.9.68.5 [Firefox 1.0.5/20050715]") 20.43.15 Join Stryke` [0] (~Chairman8@cpe-24-168-110-99.si.res.rr.com) 20.51.56 Quit lodesi ("Leaving") 20.52.49 Join lodesi [0] (~moi@62.34.146.180) 21.04.28 Join KasKaraK [0] (~KasKaraK@34.34.119-80.rev.gaoland.net) 21.06.26 Quit einhirn (Read error: 104 (Connection reset by peer)) 21.08.35 Join einhirn [0] (Miranda@carlsberg.heim2.tu-clausthal.de) 21.09.08 *** Saving seen data "./dancer.seen" 21.16.46 Join [-AIR-] [0] (air@host86-130-23-252.range86-130.btcentralplus.com) 21.16.48 Nick [-AIR-] is now known as west-acre (air@host86-130-23-252.range86-130.btcentralplus.com) 21.17.10 # hey just got back from hols. wots bin hapnin in rockbox over like the past two weeks? the major things? 21.22.42 Quit KasKaraK_ (Read error: 110 (Connection timed out)) 21.22.56 # for iriver? anyone? please... 21.23.07 # ok ill check the logs :P 21.31.28 # Hmm, the peak meter is working 21.31.35 # it was easy thing to do.. maybe i will commit soon 21.31.40 # nice 21.31.53 # congratulation ;) 21.31.57 # :D 21.33.57 Join KasKaraK_ [0] (~KasKaraK@34.34.119-80.rev.gaoland.net) 21.42.29 Quit KasKaraK (Read error: 60 (Operation timed out)) 21.51.07 Join KasKaraK [0] (~KasKaraK@34.34.119-80.rev.gaoland.net) 21.56.05 Nick CheeseBurgerMan is now known as CBM-away (~youshould@tc2-225-085.altelco.net) 22.00.39 # Hmm, it's not yet working as expected.. :P 22.00.56 # how should i calculate the current peak from the sample stream? 22.02.51 # i need calculate an average? 22.05.07 Join Coldtoast [0] (~edan@ppp111-3.lns1.hba1.internode.on.net) 22.08.50 Quit KasKaraK_ (Read error: 110 (Connection timed out)) 22.09.11 Quit KasKaraK (Read error: 60 (Operation timed out)) 22.17.00 Join webguest44 [0] (~18d79b85@labb.contactor.se) 22.17.04 Join [Nath] [0] (~nath@host-84-9-13-87.bulldogdsl.com) 22.17.31 Quit CBM-away (Read error: 54 (Connection reset by peer)) 22.18.12 # ok is there a way to shuffle ALL songs, not just the ones in a directory? 22.19.16 Part [Nath] 22.21.19 Quit webguest44 (Client Quit) 22.21.58 Join KasKaraK [0] (~KasKaraK@34.34.119-80.rev.gaoland.net) 22.25.57 # yep 22.26.16 # create a playlist in the root and enable shuffle 22.26.46 # oops. he left 22.32.03 Quit KasKaraK ("KasKaraK") 22.58.52 Join Bagder [0] (~daniel@1-1-5-26a.hud.sth.bostream.se) 23.07.24 Quit Stryke` (Read error: 60 (Operation timed out)) 23.09.10 *** Saving seen data "./dancer.seen" 23.26.40 Join XavierGr [0] (~XavierGr@ppp49-adsl-96.ath.forthnet.gr) 23.28.22 Join matsl [0] (~matsl@1-1-4-2a.mal.sth.bostream.se) 23.51.51 Quit lodesi ("Leaving")