[00:09:38] *** Quits: Kebianizao (~kvirc@120.12.219.87.dynamic.jazztel.es) (Quit: Estaba usando KVIrc KVIrc Equilibrium 4.2.0, revision: 420, sources date: 20120701, built on: 2013-08-29 10:52:41 UTC 420 http://www.kvirc.net/) [01:27:23] *** Joins: bcobco (~bcobco@77.225.204.119) [03:06:24] *** Quits: [Saint] (~saint@rockbox/staff/saint) (Ping timeout: 264 seconds) [03:18:50] *** Joins: [Saint] (~saint@rockbox/staff/saint) [03:20:30] *** Quits: [Saint] (~saint@rockbox/staff/saint) (Read error: Connection reset by peer) [03:21:16] *** Joins: [Saint] (~saint@rockbox/staff/saint) [04:07:48] *** Quits: bcobco (~bcobco@77.225.204.119) () [06:26:05] *** Quits: TheSeven (~quassel@rockbox/developer/TheSeven) (Ping timeout: 264 seconds) [06:27:14] *** Joins: TheSeven (~quassel@rockbox/developer/TheSeven) [06:58:48] *** Quits: steffengy (~quassel@p5088FA47.dip0.t-ipconnect.de) (Disconnected by services) [06:58:49] *** Joins: steffengy1 (~quassel@p57B49EF1.dip0.t-ipconnect.de) [09:24:39] *** Quits: APLU (~mulx@2a01:e34:ee29:12b0::10) (Ping timeout: 252 seconds) [09:31:04] *** Joins: APLU (~mulx@2a01:e34:ee29:12b0::10) [13:21:05] *** Joins: bcobco (~bcobco@77.225.204.119) [13:21:32] *** Joins: goom (~goomba@cpe-72-177-176-215.satx.res.rr.com) [13:23:13] *** Parts: goom (~goomba@cpe-72-177-176-215.satx.res.rr.com) () [13:36:07] *** Joins: r100 (c3559282@gateway/web/freenode/ip.195.85.146.130) [13:39:00] hi guys, have been using r859 for a long time without any problem, but I was just curious: is a new release of EmCore likely for the near future? I saw quite some activity in the code review (SVN) [13:39:49] yes, we're working on a couple of things [13:39:55] some bug fixes, but also new features [13:40:04] emcore now has its own USB disk mode [13:40:23] we'll be looking into adding SMART support to that [13:41:04] wow, great job! [13:41:11] it's also quite possible that dualbooting the original firmware will work soon [13:41:18] there's been a lot of progress on that front recently [13:42:07] rockbox finally got its USB drivers fixed on ipod classic, on nano2g they still seem to be a bit flaky. that needs some more diagnosis... [13:42:27] i.e. the next emcore can ship with an up-to-date rockbox again [13:43:01] battery monitoring will probably be improved as well (proper charging state detection, more accurate battery state estimation, firewire charging) [13:43:20] amazing! so dualboot on the Classic you mean? [13:43:23] yes [13:43:40] we squashed a number of problems that were preventing that [13:44:00] and USB drivers fixed on the Classic means no more 'unrecognised device' on certain computers? [13:44:01] booting the original disk mode already works, the main firmware still doesn't, but it's quite possible that we'll get that fixed as well [13:44:22] current rockbox's USB mode was mostly unusable on windows-based computers due to some bugs [13:44:27] that seems to be mostly fixed now [13:45:39] and then we're going to do the final step towards finishing the rockbox port: get it rid of emcore ;) [13:46:12] we already have a rockbox bootloader, but we still need to add dualboot support to that [13:46:28] this is such good news! You guys rock! I still use my classic every single day [13:46:30] then we can rework the boot process to work similar to the other ipods, without emcore in between [13:46:49] and then finally integrate the installation process into the rockbox utility :) [13:47:13] but i guess this is much more difficult compared to the ipod video right? because it's encrypted [13:47:40] the encryption itself isn't much of a problem since we've been able to crack it [13:47:51] some other things however are: [13:48:14] the hardware is vastly different from the older ipods, so you can't just reuse most of the code, but have to work out every detail again [13:48:42] the hardware also isn't documented at all, i.e. all of that needs to be reverse engineered from disassemblies of the apple firmware [13:49:49] the boot process isn't vulnerable on the step that loads the main firmware, so we need to get our bootloader in at an earlier stage, which in turns means that we have to take care of more of the hardware initialization (that's also why dualboot is not working right out of the box) [13:50:19] and it also means that we can't just install our bootloader by writing to a few sectors of the firmware partition, but instead have to flash it through DFU mude, which complicates the installation process [13:50:34] I see, so it's very low-level [13:51:01] most of the bits and pieces that are needed to finally finish this project have been figured out in the meantime, it's now mostly a task of putting them together and wrapping it all up [13:51:10] *** Quits: bcobco (~bcobco@77.225.204.119) (Remote host closed the connection) [13:51:32] *** Joins: bcobco (~bcobco@77.225.204.119) [13:52:06] would it help if i would send one or two Classic motherboards to you? Or are you beyond the point of bricking something? [13:53:28] TheSeven: what changes did you make in order to boot the original disk mode? can you post a patch somewhere? [13:56:31] user890104: initialize SysI, enable I2C clock gate (they seem to keep that on all the time and forget to enable it initially in the main firmware), and enable I2C IRQ enable bit in the I2C regs (which seems to have moved to bit 9 of that reg, used to be bit 6) [13:57:13] r100: I don't think we need mainboards for the steps that I outlined above [13:57:48] but maybe someone who wants to work on a real SD card mod might need one for HDD connector pinout probing or something [13:58:58] wodz (from #rockbox) was considering to look into that, however he's having trouble finding a source for the right kind of connector etc. [14:02:31] *** Quits: r100 (c3559282@gateway/web/freenode/ip.195.85.146.130) (Ping timeout: 246 seconds) [14:18:38] *** Quits: bcobco (~bcobco@77.225.204.119) (Remote host closed the connection) [14:19:03] *** Joins: bcobco (~bcobco@77.225.204.119) [15:12:05] *** Joins: r100 (c3559282@gateway/web/freenode/ip.195.85.146.130) [15:13:03] *** Joins: r100_ (c3559282@gateway/web/freenode/ip.195.85.146.130) [15:13:50] TheSeven: do you think the future rockbox bootloader for the classic can improve battery life? for example from a more advanced cpu frequency scaling? [15:14:53] i mean, it's already working very well at the moment, but 54 MHz seems high to play FLAC for example [15:16:19] The bootloader has no influence on that [15:16:22] *** Quits: r100 (c3559282@gateway/web/freenode/ip.195.85.146.130) (Ping timeout: 246 seconds) [15:17:04] ah okay [15:28:31] r100_: 54MHz is the lowest we can go without affecting timers, playback sampling rate, ... [15:29:07] memory interface clocking, lcd access, likely breaking the usb and hdd interfaces due to bus congestion [15:29:28] I also doubt that going any lower will yield significant savings [15:30:11] the clock freq itself doesn't directly impact battery life, it's the core voltage that does, which can be reduced with lower clock freqs [15:30:25] TheSeven: yeah I'm not an expert and just assumed that because the iPod Video could clock back to 30 MHz or so the Classic would be able to do the same, but like you mentioned earlier the hardware is different in a lot of ways [15:30:48] we are at s point where other parts of the chip would go unstable if we would go lower [15:31:31] and the cpu isn't "wasting" all those clock cycles, it will be sleeping most of the time, consuming very little power [15:32:00] apple doesn't do frequency scaling at all and their battery life isn't that much worse [15:32:31] my old classic was working fine on 54MHz at 0.950V, but the one I currently have crashes with that build and works fine on the daily on 54MHz at 1.050V [15:33:23] yes, there are always little device to device variations [15:33:44] also I think the power manager can't go below 0.9V anyway [15:34:16] yes just like with overclocking, some yields are good, others are a bit less flexible [15:34:43] the reason for switching to a rockbox bootloader is mostly making the installation process easier and more automated [15:35:43] so then less people are scared off to try it on their Classic :) [15:37:57] especially if it can dualboot and doesn't wipe any data [15:39:21] yes I remember that is one the requirements to label any port as stable, impressive to already have this on so many devices [15:39:26] *** Quits: bcobco (~bcobco@77.225.204.119) (Remote host closed the connection) [15:39:48] *** Joins: bcobco (~bcobco@77.225.204.119) [15:43:40] if the hardware encryption is hacked, would it then be possible to make accessories such as the 30-pin remote work? [16:51:12] *** Quits: r100_ (c3559282@gateway/web/freenode/ip.195.85.146.130) (Quit: Page closed) [18:43:55] *** Quits: bcobco (~bcobco@77.225.204.119) (Remote host closed the connection) [18:44:18] *** Joins: bcobco (~bcobco@77.225.204.119) [22:41:45] *** Joins: user890104_ (~Venci@unaffiliated/user890104) [22:41:46] *** Server sets mode: +nt [22:43:12] *** Quits: user890104 (~Venci@unaffiliated/user890104) (Ping timeout: 240 seconds) [22:43:12] *** Quits: el3ctrik-away (~el3ctrik@2a00:1c10:5:202:216:3eff:fe98:c8f1) (Ping timeout: 240 seconds) [22:43:12] *** user890104_ is now known as user890104 [22:43:14] *** Quits: krnlyng (~liar@83.175.90.24) (Ping timeout: 240 seconds) [22:44:09] *** Joins: el3ctrik-away (~el3ctrik@2a00:1c10:5:202:216:3eff:fe98:c8f1) [22:44:11] *** Joins: krnlyng (~liar@83.175.90.24) [22:44:32] *** el3ctrik-away is now known as el3ctrik [23:52:29] *** Quits: el3ctrik (~el3ctrik@2a00:1c10:5:202:216:3eff:fe98:c8f1) (*.net *.split) [23:54:13] *** Quits: bcobco (~bcobco@77.225.204.119) () [23:57:18] *** Joins: el3ctrik (~el3ctrik@2a00:1c10:5:202:216:3eff:fe98:c8f1) [23:58:08] *** Quits: el3ctrik (~el3ctrik@2a00:1c10:5:202:216:3eff:fe98:c8f1) (*.net *.split)