Re: [Ipodlinux-devel] new ipod, etc

[PALFFY D. <dpa...@ra...>]

> I'll skip the initrd stuff.  Seems you've got a much better solution
> there :)

Yes, I don't have to relink and install the kernel to update a file on the
initrd...

> I think the remote connector has the same connectors as the 2g iPods, I
> think the only difference is a re-arrangement.  I remember there were
> some close-up pictures that showed the connectors and didn't think there
> were any extra contacts.

Sure it's different. The new remote has 8 contacts, 4 on the jack plug,
and 4 on the side. The old one had only six.

> Thats quite interesting but also strange.  I hadn't thought either had
> changed much but if they have it should be easy enough sort out.  I will
> have to have a closer look at the diagnostic in v2.  This may also be
> the reason why the 2.1 firmware doesn't boot on 2g hardware...

I'd thank you very much, since I've never done any arm (dis)assembly, so
it would take me much more time...

> > What works: keyboard (I've only used wait_for_action() to slow down the
> > boot process), IDE, the serial ports seem to be detected (or are they hard
> > coded?), and the fb. patch_fw works well with firmware 2.1 if the check
> > for 1.2x is disabled. BTW, what's the second boot img? A flash updater?
> > When does it get booted? And what's the difference between addr and
> > loadAddr in the image structure?

> I never fully reverse engineered the fields in the boot loader table.  I
> got those names from the firmware (I think!) but I didnt work it out
> fully.

OK. The bootloader is in flash. It looks for some key combinations (forced
firewire, fsck, diag), if any of these found, loads the appropriate image
from flash, else loads the first image from the disk? Do I understand it
correctly? Aren't there any more escape sequences? Or some fixed entry
points into flash to do basic disk input? Because if there are, it would
be much easyer to make a boot loader to load different images.

--
Dani
			...and Linux for all.