[01:06:53] *** Joins: [Saint_] (~saint@rockbox/staff/saint) [01:11:02] *** Quits: [Saint] (~saint@rockbox/staff/saint) (Ping timeout: 246 seconds) [01:12:04] *** Quits: TheSeven (~quassel@rockbox/developer/TheSeven) (Ping timeout: 260 seconds) [01:13:18] *** Joins: TheSeven (~quassel@rockbox/developer/TheSeven) [02:01:09] *** [Saint_] is now known as [Saint] [04:32:55] What is FreeMyiPod written in> [04:33:46] C and asm [04:37:41] *** Quits: franklin (~franklin@cpe-071-071-071-105.triad.res.rr.com) (Remote host closed the connection) [04:44:40] ahh [04:44:49] asm for the bootloader? [06:15:32] *** Joins: steffengy (~quassel@p5088F130.dip0.t-ipconnect.de) [06:18:40] *** Quits: steffengy1 (~quassel@p5088FA06.dip0.t-ipconnect.de) (Ping timeout: 260 seconds) [06:55:06] *** Quits: TheSeven (~quassel@rockbox/developer/TheSeven) (Ping timeout: 250 seconds) [06:56:26] *** Joins: TheSeven (~quassel@rockbox/developer/TheSeven) [08:46:07] *** Joins: draft (~draft@83-245-226-15-nat-p.elisa-mobile.fi) [08:48:06] is there any hope of getting emCORE/Rockbox to run on Nano 4G? i saw some activity on emCORE SVN for Nano 4G. [09:13:21] *** Quits: draft (~draft@83-245-226-15-nat-p.elisa-mobile.fi) (Quit: leaving) [09:14:00] *** Joins: draft (draft@irc.disharmony.fi) [09:28:29] draft: yes, if you disassmble parts of the original firmware, and write some drivers [09:29:08] if only i had skillz to do that :) [09:29:52] some of us have skills, but this requires an enormous amount of time [09:29:56] so the bootloader is cracked already.. [09:30:11] yeah, we can execute third-party code [09:30:11] the drivers are missing? [09:30:20] we don't have drivers for the flash memory [09:30:32] so everything is lost on reboot [09:30:34] i saw a photo with emCORE running on Nano 4G.. that got me interested. [09:30:57] and we need to upload the exploit again via USB (a.k.a. "tethered jailbreak") :) [09:31:43] so you need to boot the Nano always with USB cable plugged to activate the exploit? [09:31:46] that's not very handy. [09:32:01] yes, at the moment [09:32:07] it's only useful for development [09:32:26] also, there's no audio coded driver [09:32:33] so it can't be used as a music player [09:32:39] i had Classic 160GB iPod with emCORE + Rockbox.. i was very satisfied with it. but it broke. :/ [09:33:10] why there haven't been "stable" release for years? [09:33:27] there weren't any changes in a while [09:33:33] i almost thought there's no one working to get them supported anymore... [09:33:58] now we're wrapping up everything, adding some new features, and preparing a final release [09:34:25] we're going to use part of emcore as a rockbox bootloader [09:34:37] so emcore won't be required to boot rockbox on the classics [09:34:50] which will also simplify the rockbox installation process [09:38:20] what does emCORE actually do between Rockbox and the hardware? [09:39:12] i wonder if gtkpod works on Nano 4G... [09:39:22] i just fucking hate the iTunes bloatware shit [09:39:35] it should work [09:40:05] emcore initialises some of the hardware, reads rockbox from the hdd into the ram, and jumps to it [09:40:37] why don't you integrate these methods directly to Rockbox? [09:40:41] it's a very complicated firmware that does a rather simple task - booting other firmware :) [09:40:58] that's work in progress currently [09:42:09] http://www.freemyipod.org/wiki/Todo_list#1G.2F2G.2F3G_Classic [10:00:30] how big group is working on emCORE at the moment? [10:02:55] draft: mainly 2-3 people [10:04:02] emcore was primarily intended as a development tool / platform [10:04:27] but it was somewhat trivial to write a bootloader application for it, and would have been more effort to port over all the code from emcore to rockbox [10:04:44] ok i get it.. but anyways i really appreciate what you guys are doing! [10:04:51] this also allowed us to circumvent some of rockbox's guidelines for the time being [10:05:06] but now we're wrapping it all up to make the installation process more simple [10:05:38] yeah it probably was a good choice to keep emCORE separate from Rockbox development as i think about it. [10:17:53] reverse engineering unknown hardware is probably very hard [10:18:22] and writing drivers is probably little boring? [10:18:49] *** Joins: bcobco (~bcobco@77.228.124.149) [10:20:36] writing the drivers isn't really a problem once you have figured out how the hardware works [10:21:01] so i'll just have to wait for the support to hopefully appear in emCORE. i'll go and buy some other player. i think the apple hardware is very good but i hate iTunes. :/ [10:21:10] actually you typically figure out the hardware by writing code for it that's poking around, and checking what happens [10:21:28] so once you know how the hardware works, you typically have a somewhat working driver already [10:21:45] i also don't like locked proprietary hardware idea. they should allow users to install CFW if they want. [10:22:04] i'm a Commodore 64 scener [10:22:12] i [10:23:06] i've seen some quite wild hacking :) i remember when SounDemon wrote a displayer for a picture, but he didn't even know that in what format the picture was. [10:24:00] it was fun to see someone poking around and seeing the picture as corrupted shit.. then after some fiddling and poking around. voéla. he got it to work. [11:18:06] *** Quits: APLU (~mulx@eva.aplu.fr) (Quit: !sucide) [12:35:04] *** Quits: bcobco (~bcobco@77.228.124.149) (Remote host closed the connection) [12:35:31] *** Joins: bcobco (~bcobco@77.228.124.149) [13:47:01] *** Joins: APLU (~mulx@eva.aplu.fr) [13:54:45] *** Quits: bcobco (~bcobco@77.228.124.149) (Remote host closed the connection) [13:55:29] *** Joins: bcobco (~bcobco@77.228.124.149) [15:10:42] *** Quits: bcobco (~bcobco@77.228.124.149) (Remote host closed the connection) [15:11:04] *** Joins: bcobco (~bcobco@77.228.124.149) [15:39:29] *** Quits: bcobco (~bcobco@77.228.124.149) (Remote host closed the connection) [15:39:53] *** Joins: bcobco (~bcobco@77.228.124.149) [15:49:58] heh [15:50:08] FMI team is doing a great job :-) [15:50:24] My 6G is working finely on OSX / Linux / Windows [15:51:43] <- wishes he could write asm / driver code [15:57:58] it's never too late [15:58:16] i didn't know even a bit of asm 2 years ago [16:32:39] Ecaz: technically you don't need to be able to write ASM code [16:32:45] you need to be able to read it though [16:32:52] and writing it is typically easier than reading it :P [16:46:31] oh [16:46:35] that's odd [16:46:49] what are the drivers written in then, C> [16:47:02] Could you have written the driver in Python if you so chose? [16:51:16] no, because pythong doesn't run on that device [16:51:22] most code is written in C [16:51:38] however you have to read disassemblies of apple's original firmware to figure out how to access the hardware [16:54:23] reading assembly written by a human is easy, reading assembly written by a compiler, and then optimized is hard [16:54:48] we're having the latter case when we disassemble apple's code [18:36:39] Ahh [18:37:30] but the firmware just executes the drivers, so can't you still write use linux for the OS and write the front-end in python [18:37:42] im just curious is all [19:34:54] *** Quits: bcobco (~bcobco@77.228.124.149) (Remote host closed the connection) [19:35:18] *** Joins: bcobco (~bcobco@77.228.124.149) [20:52:34] if you port linux to it, yes. you would be able to write the software in python [20:52:48] ah [20:52:49] right [20:53:49] *** Joins: n1s (~n1s@rockbox/developer/n1s) [22:19:28] *** Quits: bcobco (~bcobco@77.228.124.149) (Remote host closed the connection) [22:19:53] *** Joins: bcobco (~bcobco@77.228.124.149) [23:50:49] *** Quits: n1s (~n1s@rockbox/developer/n1s) (Quit: Ex-Chat)