You can subscribe to this list here.
2003 |
Jan
|
Feb
(9) |
Mar
(21) |
Apr
(12) |
May
(11) |
Jun
(6) |
Jul
(3) |
Aug
|
Sep
(10) |
Oct
(20) |
Nov
(32) |
Dec
(41) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(48) |
Feb
(27) |
Mar
(120) |
Apr
(69) |
May
(15) |
Jun
(1) |
Jul
(6) |
Aug
(1) |
Sep
(1) |
Oct
(6) |
Nov
(2) |
Dec
(4) |
2005 |
Jan
|
Feb
(10) |
Mar
(1) |
Apr
(1) |
May
|
Jun
(3) |
Jul
|
Aug
(2) |
Sep
(2) |
Oct
|
Nov
(1) |
Dec
(1) |
2006 |
Jan
(3) |
Feb
(4) |
Mar
(9) |
Apr
(2) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
(2) |
Dec
(2) |
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Bernard L. <le...@bo...> - 2004-02-29 11:47:19
|
Rather than the patchfw program take a look at the newer bootloader, this supports 2.x firmware as well as 1.x. It also alows you to dual boot between the Apple firmeware and Linux. The precompiled versions are quite out-of-date now, its much better to use the CVS version which supports the 3g ipods much better. cheers, bern. On Sat, 2004-02-28 at 21:39, Icy223 wrote: > Is it possible to use a pre-compiled kernel and install it on a 2.1 > fw? It prints: Can only patch fw 1.2x. fw is 2.1 > > Is that a problem on the pre-compiled kernels part or the patch_fw? > > Is there a newer version of patch_fw > > Any help would be greatly appreciated...thanks! |
From: Icy223 <Ic...@co...> - 2004-02-28 20:43:08
|
Is it possible to use a pre-compiled kernel and install it on a 2.1 fw? = It prints: Can only patch fw 1.2x. fw is 2.1 Is that a problem on the pre-compiled kernels part or the patch_fw? Is there a newer version of patch_fw Any help would be greatly appreciated...thanks! |
From: Bernard L. <le...@bo...> - 2004-02-28 14:35:25
|
Hi all, I am pleased to announce the availability of the first demo of podzilla, a GUI for ipodlinux. The demo is very alpha, but has some basic features such as a menu system, contrast control and a file system browser. The demo requires the current CVS version of the kernel. I'm currently working on getting a new kernel release together but there are a few issues on g3 iPods still to sort out (namely audio, piezo & remote). Look for this release in a few weeks. To build the demo you need the following two modules from CVS: tools/podzilla tools/microwindows The podzilla README contains further building instructions. Some screen shots can be found on the ipodlinux webpages; <http://ipodlinux.sourceforge.net/screens.shtml>. Thanks to Damien Marchal for helping me get podzilla together. Feedback welcome! cheers, bern. |
From: Bernard L. <le...@bo...> - 2004-02-19 23:36:22
|
Hi all, I've just checked into CVS an updated version of the firmware driver. This version seems quite stable with TCP/IP and I can get reasonable transfer rates. I have also made some minor updates to the framebuffer device to support ioctls to set the contrast and backlight settings. This means that user-level applications can easily change these settings. If anyone has a 1st Gen iPod and can test the CVS version of the kernel I'd be interested to hear how it goes. cheers, bern. |
From: Bernard L. <le...@bo...> - 2004-02-18 13:41:50
|
Hi all, I have marked the old/outdated releases of the packages on the sf website as hidden so as to avoid confusion about which packages & versions are current. Since the old firmware patch program is deprecated by the new bootloader it is also no longer visible. All the source code necessary to build these old releases is in CVS if anyone requires it, in addition, the releases actually remain on the sf download servers and so can be unhidden if need be. cheers, bern. |
From: PALFFY D. <dpa...@ra...> - 2004-02-11 17:55:15
|
On Wed, 11 Feb 2004, Bernard Leach wrote: > > Hold off generates three: 0x20/0x20; 0xdf/0xff; 0x40/0xbf. The first > > interrupt from hold on won't be easy to block since it's a perfectly valid > > input from wheel motion, too. What does the apple firmware do? > > Typo fixed... thanks. > > As for the interrupts, the multiple interrupts are caused by incorrect > processing in the keyboard driver. With the patch applied I get three interrupts for hold on, too, it didn't change hold off. At hold on, the first interrupt was problematic. It always looks like a wheel movement, so your patch doesn't change anything. Also your patch doesn't change hold off behaviour. I think we should put a short delay in the interrupt handler, and read state then, since we get an interrupt on all pins, but the first one arriving is on some wheel inputs. Diags mode also does it wrong (a hold on/off sometimes causes all keys pass the test), so we can't look there... -- Daniel ...and Linux for all. |
From: Bernard L. <le...@bo...> - 2004-02-11 16:30:56
|
PALFFY Daniel <dpa...@ra...> said: > > Hi! > > > Thanks for the testing. I've commited the fix to the iPod firewire > > driver now so once the public CVS server is updated (v1.6 has the fix) > > only the #define needs to be modified. > > Thanks. I've looked at your other changes. Some comments about keyboard.c: > The 3G HOLD_SWITCH_IS_ON macro has a typo - you meant &, not &&. > Otherwise, the hold botton works a little bit more complicated than > before. Hold on generates two interrupts - source/state: 0xX0/0xff; > 0xff/0x00, where X was 4, 8 or c depending on the current wheel state. > Hold off generates three: 0x20/0x20; 0xdf/0xff; 0x40/0xbf. The first > interrupt from hold on won't be easy to block since it's a perfectly valid > input from wheel motion, too. What does the apple firmware do? Typo fixed... thanks. As for the interrupts, the multiple interrupts are caused by incorrect processing in the keyboard driver. Could you try this patch: RCS file: /cvsroot/ipodlinux/linux/arch/armnommu/mach-ipod/keyboard.c,v retrieving revision 1.4 diff -u -r1.4 keyboard.c --- keyboard.c 11 Feb 2004 15:59:48 -0000 1.4 +++ keyboard.c 11 Feb 2004 16:25:56 -0000 @@ -63,7 +63,6 @@ /* get current keypad status */ state = inb(0xcf000030); - outb(~state, 0xcf000060); #ifdef CONFIG_VT kbd_pt_regs = regs; @@ -81,6 +80,8 @@ #ifdef IPOD_3G /* hold switch on 3g causes all outputs to go low */ /* we shouldn't interpret these as key presses */ + /* nor should we flip the interrupt levels */ + outb(state ^ 0x20, 0xcf000060); goto done; #endif } @@ -95,6 +96,8 @@ } } + outb(~state, 0xcf000060); + if ( source & 0x1 ) { if ( state & 0x1 ) { #if defined(DO_SCROLLBACK) > > On the server side I will see about updating the documentation shortly. > > But basically the host nodemgr.c needs to be patched (commenting out the > > do_irm_duties) and the eth1394.c driver replaced with the one from the > > ipodlinux CVS (this already contains the patch mentioned in the manual). > > eth1394.c doesn't seem to contain the patch from the manual. Thats right.... on the iPod side the broadcast _write_ and subsequent reply are fine but it needs to translate the incoming arp requests to look like coming from a broadcast address. On the PC side we need to make sure we don't write to broadcast addresses or the iPod pukes. I could just put that patch in eth1394.c on the iPod too, perhaps that would simplify things.... BTW The Darwin equivalent of eth1394 is open source so in theory it could be modified to be compatible with our hacked up version. Any OSX hackers out there up for a challenge? cheers, bern. |
From: PALFFY D. <dpa...@ra...> - 2004-02-11 14:59:47
|
Hi! > Thanks for the testing. I've commited the fix to the iPod firewire > driver now so once the public CVS server is updated (v1.6 has the fix) > only the #define needs to be modified. Thanks. I've looked at your other changes. Some comments about keyboard.c: The 3G HOLD_SWITCH_IS_ON macro has a typo - you meant &, not &&. Otherwise, the hold botton works a little bit more complicated than before. Hold on generates two interrupts - source/state: 0xX0/0xff; 0xff/0x00, where X was 4, 8 or c depending on the current wheel state. Hold off generates three: 0x20/0x20; 0xdf/0xff; 0x40/0xbf. The first interrupt from hold on won't be easy to block since it's a perfectly valid input from wheel motion, too. What does the apple firmware do? > On the server side I will see about updating the documentation shortly. > But basically the host nodemgr.c needs to be patched (commenting out the > do_irm_duties) and the eth1394.c driver replaced with the one from the > ipodlinux CVS (this already contains the patch mentioned in the manual). eth1394.c doesn't seem to contain the patch from the manual. -- Daniel ...and Linux for all. |
From: Robert D <ro...@op...> - 2004-02-11 08:13:44
|
As soon as i get my linux system up and running properly (i might even boot up a knoppix cd just so i can try this out :D) i will test this out. If it works i am very very very excited. Has anyone else tested the new patches? By the way, how did you find out that that is what was wrong? Robert D > ----- Original Message ----- > From: "PALFFY Daniel" <dp...@ra...> > To: <ipo...@li...> > Cc: "Bernard Leach" <le...@bo...> > Sent: Wednesday, February 11, 2004 12:46 AM > Subject: [Ipodlinux-devel] 3g firewire success > > > > > > Hi! > > > > The problem with the 3g ipod forewire driver seems to be found. > > > > The hardware is capable to do direct DMA transfers between the firewire > > controller and the hard disk, and to support this, we think that the apple > > firmware does some interrupt setup in the firewire init routine. This > > kills the ide driver under linux (and is not used anyways), so it had to > > be removed. > > > > Quick howto: > > > > - Take the 2.4.24-uc0 kernel, and use the current ipodlinux CVS (older > > versions wont work). > > - edit arch/armnommu/mach-ipod/tsb42aa82.c: > > #undef IPOD_2G, and #define IPOD_3G on lines 37-38 > > comment out lines 1036-1038: (Bern, you might want to commit this) > > /* outl(inl(0xcf00000c) | (1<<7), 0xcf00000c); > > outl(inl(0xcf00001c) | (1<<7), 0xcf00001c); > > outl(inl(0xcf00002c) & ~(1<<7), 0xcf00002c); */ > > - build the kernel and modules and install these. > > > > On the host side you will need a 2.4 kernel (2.6 doesn't work and causes > > panics on the ipod!). If you have 2.4.21 or later (IIRC), put an #if 0 > > around the body of nodemgr_do_irm_duties() in drivers/ieee1394/nodemgr.c. > > Copy drivers/ieee1394/eth1394.[ch] over from the ipodlinux CVS tree into > > your kernel sources (the stock version doesn't work). Apply the patch from > > http://ipodlinux.sourceforge.net/manual.shtml to eth1394.c and build the > > kernel for the host. Now everything should work as described in the > > docs, telnet, etc work fine. > > > > -- > > Daniel > > ...and Linux for all. > > > > > > > > ------------------------------------------------------- > > The SF.Net email is sponsored by EclipseCon 2004 > > Premiere Conference on Open Tools Development and Integration > > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > > http://www.eclipsecon.org/osdn > > _______________________________________________ > > iPodlinux-devel mailing list > > iPo...@li... > > https://lists.sourceforge.net/lists/listinfo/ipodlinux-devel > |
From: Bernard L. <le...@bo...> - 2004-02-10 21:33:30
|
Hey Daniel, Thanks for the testing. I've commited the fix to the iPod firewire driver now so once the public CVS server is updated (v1.6 has the fix) only the #define needs to be modified. On the server side I will see about updating the documentation shortly. But basically the host nodemgr.c needs to be patched (commenting out the do_irm_duties) and the eth1394.c driver replaced with the one from the ipodlinux CVS (this already contains the patch mentioned in the manual). cheers, bern. On Tue, 2004-02-10 at 14:46, PALFFY Daniel wrote: > Hi! > > The problem with the 3g ipod forewire driver seems to be found. > > The hardware is capable to do direct DMA transfers between the firewire > controller and the hard disk, and to support this, we think that the apple > firmware does some interrupt setup in the firewire init routine. This > kills the ide driver under linux (and is not used anyways), so it had to > be removed. > > Quick howto: > > - Take the 2.4.24-uc0 kernel, and use the current ipodlinux CVS (older > versions wont work). > - edit arch/armnommu/mach-ipod/tsb42aa82.c: > #undef IPOD_2G, and #define IPOD_3G on lines 37-38 > comment out lines 1036-1038: (Bern, you might want to commit this) > /* outl(inl(0xcf00000c) | (1<<7), 0xcf00000c); > outl(inl(0xcf00001c) | (1<<7), 0xcf00001c); > outl(inl(0xcf00002c) & ~(1<<7), 0xcf00002c); */ > - build the kernel and modules and install these. > > On the host side you will need a 2.4 kernel (2.6 doesn't work and causes > panics on the ipod!). If you have 2.4.21 or later (IIRC), put an #if 0 > around the body of nodemgr_do_irm_duties() in drivers/ieee1394/nodemgr.c. > Copy drivers/ieee1394/eth1394.[ch] over from the ipodlinux CVS tree into > your kernel sources (the stock version doesn't work). Apply the patch from > http://ipodlinux.sourceforge.net/manual.shtml to eth1394.c and build the > kernel for the host. Now everything should work as described in the > docs, telnet, etc work fine. > > -- > Daniel > ...and Linux for all. > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > iPodlinux-devel mailing list > iPo...@li... > https://lists.sourceforge.net/lists/listinfo/ipodlinux-devel > |
From: PALFFY D. <dp...@ra...> - 2004-02-10 13:46:16
|
Hi! The problem with the 3g ipod forewire driver seems to be found. The hardware is capable to do direct DMA transfers between the firewire controller and the hard disk, and to support this, we think that the apple firmware does some interrupt setup in the firewire init routine. This kills the ide driver under linux (and is not used anyways), so it had to be removed. Quick howto: - Take the 2.4.24-uc0 kernel, and use the current ipodlinux CVS (older versions wont work). - edit arch/armnommu/mach-ipod/tsb42aa82.c: #undef IPOD_2G, and #define IPOD_3G on lines 37-38 comment out lines 1036-1038: (Bern, you might want to commit this) /* outl(inl(0xcf00000c) | (1<<7), 0xcf00000c); outl(inl(0xcf00001c) | (1<<7), 0xcf00001c); outl(inl(0xcf00002c) & ~(1<<7), 0xcf00002c); */ - build the kernel and modules and install these. On the host side you will need a 2.4 kernel (2.6 doesn't work and causes panics on the ipod!). If you have 2.4.21 or later (IIRC), put an #if 0 around the body of nodemgr_do_irm_duties() in drivers/ieee1394/nodemgr.c. Copy drivers/ieee1394/eth1394.[ch] over from the ipodlinux CVS tree into your kernel sources (the stock version doesn't work). Apply the patch from http://ipodlinux.sourceforge.net/manual.shtml to eth1394.c and build the kernel for the host. Now everything should work as described in the docs, telnet, etc work fine. -- Daniel ...and Linux for all. |
From: Terje W. <wie...@sa...> - 2004-02-10 04:44:43
|
Hello all! As a new member on the list, I just wanted to introduce myself. My name is Terje Wiesener, I'm studying at the Norwegian University of=20 Technology and Science in Trondheim. I just bought an Ipod, and the thought of getting it to run linux is=20 really thrilling! I have some prior experience with linux, that is, I've been running Debia= n=20 on some of my machines the last few years, and I've installed and=20 maintained many different flavours of linux on friends' computers. I also= =20 have some programming experience in C/C++, Java, PHP, Python etc, but I=20 have never done any real programming under linux, nor have I ever done=20 anything more advanced with the kernel than to configure and build a plai= n=20 2.4 or 2.6 kernel. What would be the best way for me to get involved in this project? Also, is the latest kernel and bootloader compatible with the newest=20 "regular" ipods (ie, the 15 GB version with the docking connector)? Is=20 there any chance of rendering my ipod unusable by installing linux on it? What is the status of userland apps? Is there a running GUI for instance? Best regards, Terje Wiesener |
From: Jim W. <js...@bl...> - 2004-02-10 03:13:32
|
> the problem with this input scheme is that the scroll wheel (and touch > wheel) > only detect rotational motions. >> Apparently theyve offered to license their technology to Apple. >> Thought the >> idea might be useful to us for text input under Linux... License it? Well, if I'd adapted it, I'd license it too - this isn't new. This is basically Quickwriting, and I don't know who (if anyone) "owns" that idea (maybe the same people here. And do we really know *what* the touch wheel detects? It could possibly truely detect only rotational motion (some arrangement of capacitance-sensing running underneather that cancel each other in sequence somehow - I don't know, just a very vague idea) Or it could have circuitry to detect a touch *anywhere* (maybe like a trackpad - can a trackpad do any kind od absolute positioning?), in which case one could detect where the finger hits the wheel, when it leaves it and very quickly touches the center "button", then leaves the button and touches the wheel somewhere else. The two points define your letter. Jim Witte js...@bl... Indiana University CS |
From: Samuel O. <or...@fa...> - 2004-02-09 10:23:16
|
Hi Bernard, Thanks for the answer. So you basically disassembled the firmware and poke around it, right ? I'll go the same way, then... Another question: As far as I understand, the PP5002 is a dual ARM7 core chipset. By reading the current ipodlinux code, we just use one of this ARM7. I guess Apple firmware uses the second one as a dedicated audio decoding chip. If so, do you have any plans on trying to access both ARM7 too, and sticking a userland audio player to one of them ? Cheers, Samuel. Bernard Leach wrote: >Hi Samuel, > >the information on the PP5002 has been derived by reverse engineering the >Apple firmware (and much experiment!). > >Some parts of the firmware are quite helpful in the reverse eng process, e.g. >in the bootloader there are "command" functions with nice useage strings that >implement things like "power down LCD", or sound piezo. Other parts are not >so helpful and brute force is the only technique. > >I have requested the development docs from PortalPlayer and although they said >they would try and get them to me (without requiring a NDA) they never got >around to it. > >cheers, >bern. > >Samuel Ortiz <or...@fa...> said: > > > >>Hi guys, >> >>I got a 2.4.24-uc0 + latest ipodlinux cvs booting on my 3G ipod this >>weekend. This is an impressive work ! >>I was even more impressed when I started to look at the code. IMHO, >>writing this code without documentation nor JTAG interface is not a >>piece of cake... >>Since I now would like to contribute to this project, I need some kind >>of help. I am interested in adding some power management features to >>this kernel. Portalplayer claims that its chipset provides many power >>management hooks, but how can I get some informations about it, without >>having any useful PP5002 docs ? More generally, how did you manage to >>reverse engineer this machine ? As an example, how did you manage to >>understand that, in order to set the CPU speed to 75 Mhz, you'd have to >>do this: >> >> outl(0x02, 0xcf005008); >> outl(0x55, 0xcf00500c); >> outl(0x6000, 0xcf005010); >> outl(24, 0xcf005018); >> outl(75, 0xcf00501c); >> >>How did you know that you have to write to this specific ports ? Did you >>get all this information from Apple's firmware ? >> >>Thanks in advance for your time and answers ! >> >>Cheers, >>Samuel. >> >> >> >>------------------------------------------------------- >>The SF.Net email is sponsored by EclipseCon 2004 >>Premiere Conference on Open Tools Development and Integration >>See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. >>http://www.eclipsecon.org/osdn >>_______________________________________________ >>iPodlinux-devel mailing list >>iPo...@li... >>https://lists.sourceforge.net/lists/listinfo/ipodlinux-devel >> >> >> > > > > > > >------------------------------------------------------- >The SF.Net email is sponsored by EclipseCon 2004 >Premiere Conference on Open Tools Development and Integration >See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. >http://www.eclipsecon.org/osdn >_______________________________________________ >iPodlinux-devel mailing list >iPo...@li... >https://lists.sourceforge.net/lists/listinfo/ipodlinux-devel > > |
From: Bernard L. <le...@bo...> - 2004-02-09 10:09:19
|
Hi Samuel, the information on the PP5002 has been derived by reverse engineering the Apple firmware (and much experiment!). Some parts of the firmware are quite helpful in the reverse eng process, e.g. in the bootloader there are "command" functions with nice useage strings that implement things like "power down LCD", or sound piezo. Other parts are not so helpful and brute force is the only technique. I have requested the development docs from PortalPlayer and although they said they would try and get them to me (without requiring a NDA) they never got around to it. cheers, bern. Samuel Ortiz <or...@fa...> said: > Hi guys, > > I got a 2.4.24-uc0 + latest ipodlinux cvs booting on my 3G ipod this > weekend. This is an impressive work ! > I was even more impressed when I started to look at the code. IMHO, > writing this code without documentation nor JTAG interface is not a > piece of cake... > Since I now would like to contribute to this project, I need some kind > of help. I am interested in adding some power management features to > this kernel. Portalplayer claims that its chipset provides many power > management hooks, but how can I get some informations about it, without > having any useful PP5002 docs ? More generally, how did you manage to > reverse engineer this machine ? As an example, how did you manage to > understand that, in order to set the CPU speed to 75 Mhz, you'd have to > do this: > > outl(0x02, 0xcf005008); > outl(0x55, 0xcf00500c); > outl(0x6000, 0xcf005010); > outl(24, 0xcf005018); > outl(75, 0xcf00501c); > > How did you know that you have to write to this specific ports ? Did you > get all this information from Apple's firmware ? > > Thanks in advance for your time and answers ! > > Cheers, > Samuel. > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > iPodlinux-devel mailing list > iPo...@li... > https://lists.sourceforge.net/lists/listinfo/ipodlinux-devel > |
From: Bernard L. <le...@bo...> - 2004-02-09 10:00:13
|
Hi Jeff, the problem with this input scheme is that the scroll wheel (and touch wheel) only detect rotational motions. cheers, bern. Jeffrey Harris <jef...@cl...> said: > Hey, I was just looking around a few iPod sites and I came across this: > http://www.thumbscript.com/tsdemo/TSDemo.html > > Apparently theyve offered to license their technology to Apple. Thought the > idea might be useful to us for text input under Linux... > > Jeff > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > iPodlinux-devel mailing list > iPo...@li... > https://lists.sourceforge.net/lists/listinfo/ipodlinux-devel > -- |
From: Samuel O. <or...@fa...> - 2004-02-09 09:42:28
|
Hi guys, I got a 2.4.24-uc0 + latest ipodlinux cvs booting on my 3G ipod this weekend. This is an impressive work ! I was even more impressed when I started to look at the code. IMHO, writing this code without documentation nor JTAG interface is not a piece of cake... Since I now would like to contribute to this project, I need some kind of help. I am interested in adding some power management features to this kernel. Portalplayer claims that its chipset provides many power management hooks, but how can I get some informations about it, without having any useful PP5002 docs ? More generally, how did you manage to reverse engineer this machine ? As an example, how did you manage to understand that, in order to set the CPU speed to 75 Mhz, you'd have to do this: outl(0x02, 0xcf005008); outl(0x55, 0xcf00500c); outl(0x6000, 0xcf005010); outl(24, 0xcf005018); outl(75, 0xcf00501c); How did you know that you have to write to this specific ports ? Did you get all this information from Apple's firmware ? Thanks in advance for your time and answers ! Cheers, Samuel. |
From: Jeffrey H. <jef...@cl...> - 2004-02-09 08:26:05
|
Hey, I was just looking around a few iPod sites and I came across this: http://www.thumbscript.com/tsdemo/TSDemo.html Apparently theyve offered to license their technology to Apple. Thought the idea might be useful to us for text input under Linux... Jeff |
From: Robert D <ro...@op...> - 2004-02-06 10:19:15
|
Yup, I have, it works fine! Robert D ----- Original Message ----- From: "Samuel Ortiz" <or...@fa...> To: <ipo...@li...> Sent: Friday, February 06, 2004 8:11 PM Subject: [Ipodlinux-devel] firmware 2.x > Hi guys, > > Has someone managed to boot a linux kernel on a 3G ipod with 2.x firmware ? > > Thanks, > Samuel. > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > iPodlinux-devel mailing list > iPo...@li... > https://lists.sourceforge.net/lists/listinfo/ipodlinux-devel |
From: Samuel O. <or...@fa...> - 2004-02-06 10:07:40
|
Hi guys, Has someone managed to boot a linux kernel on a 3G ipod with 2.x firmware ? Thanks, Samuel. |
From: damien m. <Dam...@li...> - 2004-02-04 08:36:37
|
Bernard Leach wrote: > Hi Damien, > > one of the most common questions I get is what about a GUI so I'm sure a > few people would be interested ;) If you'd like I can host your work as > part of the ipodlinux project. > > Ideally I had thought something like microwindows or nanogui would be > the way to go, but a custom library would also be fine. > > As for your questions, I'm not too sure about the speed of the iPod > display. Certainly updating the changed portions of the screen is much > faster than redrawing the entire display. Up till now I don't know that > anyone has done much experimentation (at least publically!) with the > display capabilities of the iPod. > > As for userland API versus kernel. It would be nice to keep > applications written to standard APIs etc wherever possible, the main > reason so that standard Linux apps will then "just work" but it also > keeps the emulation environment simple (in the best case a standard > Linux box!). I can imagine wrapper APIs would be useful in certain > cases, e.g. for the piezo a library wraps the serial functions into a > simple sound_piezo() type function. > > The framebuffer might also be a good case, but then just going via > /dev/fb0 should work too. > > cheers, > bern. > > On Thu, 2004-01-29 at 10:07, damien marchal wrote: > Hi bern, After watching for more than 2 seconds the nanogui project, i agree with you it should be great to port this to ipodlinux. I hope more people (g3 users) would be interrested by ipodlinux if their is a gui, even if this gui is based on a crappy graphics library at the beginning. I never do kernel programming, and it is not so simple :) . I tried to mmap() the /dev/fb0 and it didn't worked (of course). But i don't test if read()/write() is an efficient way to draw something to the fb. Hosting the gui project in ipodlinux is a good idea and i'm cleaning my source-code to do this. Cheers, Damien |
From: damien m. <Dam...@li...> - 2004-02-04 08:34:52
|
Hi Robert, Intially this interface was just a test to my graphics library. And i have to say it is a pleasure to navigate with the wheel :). Bernard purpose to host the the gui projet to the ipodlinux site and i think it is the best solution. It have to some check and find that Amstrad cpc was a 4 colors computer maybe we could grab some free artworks. A also try to port a cpc emulator but the result is awfull because i have to convert from 320x200x4 to 160x100x4 :) Maybe old-computer has a 160x128 video mode to port the emulator and having to a low cost a lot of games. A rogue game should be possible too... i'll have to check one :) Any ideas of what function could be good, how to launch program from the GUI with arguments (for exemple by parsing the --help options to reteive the arguments and allow selection on it or by parsing the man page associated .... ). So their is a lot of work to do. I'm currently thinking how to do a Menu-SubMenu system (like apple ipod) which to store and launch the differents functions. So, i 'll release everything as soon as possible, but i have to say that i program like a "pig" and i'm a litlle shy to allow other ppl to view it :) Cheers, Damien. Robert D wrote: > Hey, > > You emailed me a while ago asking me the same thing - kinda, unfortunetly i > lost a bunch of emails a while ago when my system went down - sorry about > that. > > Anyways - i am a windows programmer and i was going to play around with > C/C++ and making an interface for the iPod, but it looks like you beat me to > it. > > I would be very interested in helping with the project though, maybe we are > in need of a sourceforge site? Heh. > > Robert. > > ----- Original Message ----- > From: "damien marchal" <Dam...@li...> > To: <ipo...@li...> > Sent: Thursday, January 29, 2004 6:27 PM > Subject: [Ipodlinux-devel] Re: keypad problem > > > >>Hi, >> >>thank for the the advice about keypad (opening "/dev/console") now it >>work really well, i'm so proud of using the wheel in my code :) . >> >> >>I'm currently doing a little interface (gui) for my g3 ipod, currently i >>can only navigate in the directories, changing contrast with a slider, >>and starting executables. To do this i have a little graphics library >>(drawLines, putPixel, putSprite, changeContrast). >>Do some of you have similar project ? Maybe we could merge, or define a >>common interface where we could plug our functions ? >> >>Is their any people interested ? |
From: Bernard L. <le...@bo...> - 2004-02-02 20:00:58
|
Sorry for the timing Robert ;) But if it gets your gentoo system up and running faster then it seems like a good thing! I am still using the old 2.95.3 version from uclinux.org. They also have experimental gcc3 toolchains which should also be ok. Given that gcc3 works fine for straight x86 compilation I would be surprised if there were any problems with the cross-compile. cheers, bern. On Sat, 2004-01-31 at 00:36, Robert D wrote: > ----- Original Message ----- > From: "Robert D" <ro...@op...> > To: "Bernard Leach" <le...@bo...> > Sent: Saturday, January 31, 2004 9:35 AM > Subject: Re: [Ipodlinux-devel] cvs updates > > > > Why oh why did you have to release it now - just when my linux system went > > kaboom (my first experiment with gentoo). I guess i know have some real > > motivation to get gentoo up and running again. Hehe. > > > > Btw, is there any version of gcc i should avoid when building uClinux? > > > > Robert > > > > ----- Original Message ----- > > From: "Bernard Leach" <le...@bo...> > > To: <ipo...@li...> > > Sent: Thursday, January 29, 2004 11:18 AM > > Subject: [Ipodlinux-devel] cvs updates > > > > > > > > > > Hi all, > > > > > > I've just completed the first cut at migrating to the 2.4.24 kernel > > > (uClinux version) and my latest changes are now in CVS [1]. > > > > > > Sofar it seems everything works at least as it did in 2.4.20! Firewire > > > is working (on my 2nd gen iPod at least) for tcp/ip [2] and almost > > > working for sbp2. New in this version of the kernel is support for HFS+ > > > filesystems. I haven't tried it but this should allow you to run on Mac > > > iPods without conversion to FAT32. > > > > > > If anyone wants to try this on a g3 iPod I would be interested to hear > > > how it goes. There are some conditional compilations in the firewire > > > driver arch/armnommu/mach-ipod/tsb42aa82.c which may get it to work. > > > > > > I hope to do a bit more testing over the next few weeks and then see > > > about putting up a new version on sourceforge. > > > > > > cheers, > > > bern. > > > > > > [1] The changes in the public cvs server may take some time to show up. > > > [2] The iPod driver still has problems with broadcast writes, this means > > > you need to modify the PC side drivers to not send broadcasts. Put an > > > #if 0 around the code in nodemgr_do_irm_duties() in nodemgr.c. > > > > > > > > > > > > > > > ------------------------------------------------------- > > > The SF.Net email is sponsored by EclipseCon 2004 > > > Premiere Conference on Open Tools Development and Integration > > > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > > > http://www.eclipsecon.org/osdn > > > _______________________________________________ > > > iPodlinux-devel mailing list > > > iPo...@li... > > > https://lists.sourceforge.net/lists/listinfo/ipodlinux-devel > > > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > iPodlinux-devel mailing list > iPo...@li... > https://lists.sourceforge.net/lists/listinfo/ipodlinux-devel > |
From: Bernard L. <le...@bo...> - 2004-02-02 19:56:57
|
BTW the problem with the black screen on startup _should_ be fixed with the CVS version of the bootloader. If someone gets a chance to test this out on a 1g or 3g iPod I'd be interested to hear the results. cheers, bern. On Fri, 2004-01-30 at 09:14, Robert D wrote: > Did you compile in firewire? If so that is the reason. Try to recompile > again without firewire and it should work. > > Robert D. > > ----- Original Message ----- > From: "Martino di Filippo" <web...@ma...> > To: <ipo...@li...> > Sent: Thursday, January 29, 2004 7:23 AM > Subject: [Ipodlinux-devel] 3g > > > > ok, moved a further steps toward (thanks bernard!!) > > now i have another problem. > > i've installed the bootloader with apple's firmware as default. > > it loads without problems (apple logo, black screen, tux and then i get > in), > > and i can use the ipod as usually. but, when i try to load the linux > image, > > holding down rew at ipod start, it stops at the black screen before the > tux > > image. i think it's a problem of the kernel, but before trying to > recompile > > in some other way, i wondered if anyone has a hint. > > > > thanks, bye > > -- > > Martino di Filippo <matrix87> > > web...@ma... > > http://www.matrix87.com > > > > > > ------------------------------------------------------- > > The SF.Net email is sponsored by EclipseCon 2004 > > Premiere Conference on Open Tools Development and Integration > > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > > http://www.eclipsecon.org/osdn > > _______________________________________________ > > iPodlinux-devel mailing list > > iPo...@li... > > https://lists.sourceforge.net/lists/listinfo/ipodlinux-devel > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > iPodlinux-devel mailing list > iPo...@li... > https://lists.sourceforge.net/lists/listinfo/ipodlinux-devel > |
From: Bernard L. <le...@bo...> - 2004-02-02 19:53:05
|
Hi Damien, one of the most common questions I get is what about a GUI so I'm sure a few people would be interested ;) If you'd like I can host your work as part of the ipodlinux project. Ideally I had thought something like microwindows or nanogui would be the way to go, but a custom library would also be fine. As for your questions, I'm not too sure about the speed of the iPod display. Certainly updating the changed portions of the screen is much faster than redrawing the entire display. Up till now I don't know that anyone has done much experimentation (at least publically!) with the display capabilities of the iPod. As for userland API versus kernel. It would be nice to keep applications written to standard APIs etc wherever possible, the main reason so that standard Linux apps will then "just work" but it also keeps the emulation environment simple (in the best case a standard Linux box!). I can imagine wrapper APIs would be useful in certain cases, e.g. for the piezo a library wraps the serial functions into a simple sound_piezo() type function. The framebuffer might also be a good case, but then just going via /dev/fb0 should work too. cheers, bern. On Thu, 2004-01-29 at 10:07, damien marchal wrote: > Hi, > > as i said in a previous post, i have done a tiny (and buggy) graphics > library for the ipod with a pseudo emulator (in opengl) to make the > developpement easier. (i have just readed about nanogui from the mailing > list archive) > > Currently i have: > - drawHorizLines > - putPixel > - get/setContrast > - putSprite > - drawFont with font size of 6x11 et 8x8 > > as soon as debugged (the putsprite at any position give me a headache) i > 'll release this. I also have a tool to convert from header files > (exported by gimp) to ipod_sprite format. > > If you have, 4 colors artwork, fonts, images, icons > i'm very interrested in collecting them. > > > The questions now... > > Do somebody has informations about the ipod display ? > - speed in the differents mode ? > - is it better to directly render on the screen or having a double > buffer in memory (like in fb) ? > - how to render viewable basic animation ? > > For what i know, incremental update is much more viewable than deleting > everything followed by a redraw (i'm so sad that ipod haven't an GBA > display :) ) > > > The existential part know: > > Currently i disconnect the fb driver of the kernel and i directly > address the screen from an userland API. Somebody has a better solution ? > > In my point of view a usermode api that access to ipod-hardware is bad > but easier than doing fully Posix-Apm-fb-compilant. > > What is yours opinions ? > > What about doing a complete ipod-API for all hardware access (for > individual components sleep mode, get/set processor speed, screen > access, timer, keypad. As far as i know their is no protected-mode > in uClinux so their is no problem to do this. > > Cheers, > Damien Marchal. > > > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > iPodlinux-devel mailing list > iPo...@li... > https://lists.sourceforge.net/lists/listinfo/ipodlinux-devel > |