Can we get support for the 64 meg cache instead of 32 on 5g 60gig?

[orfax]

Awesome.... I tried figuring out how to compile.....  I suck....  If you need someone to test your compilation and the 64 meg buffer, I'm all for it.  Just let me know I'll give you my email address and you can email me the file.

Thanks for the offer. I have a 60 GB ipod video, so I use that for testing, but if I get something working I'll put it up here for further testing.

Now, I've compiled with memory=64, and while it boots and I can browse my files and go through most options, thats about all it does. When I try to play an mp3, I get a "codec failure" message. When I try to start a module, I get an "Incompatible model". On the info screen, I see the Buffer is at 61.303.

For any memory values over 32 I get these problems (I've tried 64, 48, 34). This may be due to memory address checks, but I'm not sure at this stage. However I set memory to 32 & 16 and that worked fine.

I'll look further.

[orfax]

... but if you show up on IRC, someone there might be able to answer...

OK, I was going to anyway in the next few days. Thanks.

[treq]

same thing here, compiling with memory=64 leads to incompatible model & codec failure....

[housebox]

i agree with that, i also tried a lot using the 64mb ram of my 5g. couldn't get it to work...

[orfax]

Can we get support for the 64 meg cache instead of 32 on 5g 60gig?

Just a quick update. It appears I have 64 MB working. The changes to get it working are:

tools/configure: set memory=64

and

firmware/crt0.S: change line 72:
mov    r1, #0x3a00
to
mov    r1, #0x7400

I believe this tells the memory controller how much memory (in pages?) to remap.

I'll post a little later with a build.

[orfax]

An experimental build can be gotten here:
ipod5g-64MB

This is a build of the 2006-05-25 23:45 CVS source with only the fix to allow the use of 64MB. It has no other patches applied.

Needless to say, its *only* for a 5th gen ipod with 64MB memory (ie 60Gig ipod video).

If anyone has any problems with it let me know.

I've used it for several hours so far without any problems.

[Markalexander]

Thanks, that's working nicely for me. 

[The_Gord]

Has anyone using this build/patch notice any significant differences/benefits?  Because what Llorean said makes a lot of sense.

[mrmagic526]

It'll help with battery life....  I suggest making two builds for the Ipod video.  One for the 30 gig and one for the 60 gig.  Since that's what determines if it has 64 meg or 32 meg.  People are smart enough to know if they have 30 or 60 gig.

[mrmagic526]

then again you have this wonderful crazyapplerumors website with this.

Just one day after learning that it is the target of a lawsuit claiming the iPod might one day possibly under certain circumstances maybe hurt some guy in Louisiana’s ears, Apple has decided to discontinue sales to stupid people.

“We did a cost/benefit analysis,” said Chief Operating Officer Tim Cook, “And it clearly is not cost effective to continue to have stupid people as our customers.”

According to a detailed analysis by Apple’s finance group, the company loses more money from having to create overly detailed documentation, defend itself against inane lawsuits and field repeated support calls asking “Is there little men in mah iMac what make it run?!” than it makes in sales to these customers.

Nitwits, morons, dunderheads, idiots and boneheads will find themselves turned away from their local Apple Store starting March 1st.

Cook said “We needed to get some procedures in place so that our sales associates could tell the difference between a chowderhead, for example, and a customer that meets our new minimum intelligence quotient for purchasing an Apple product.”

The latest lawsuit spurred the company to take action after it realized that if it could face a lawsuit over something clearly listed as a warning in the product documentation from an individual who has not been damaged, it had simply lost control of the situation.

“We just didn’t know what else to do,” Cook said.

“We considered various other scenarios, from engraving the warning on the front of the iPod, printing it on the front of the box, using giant laser cannons to etch it on the face of the moon, showing up at customers houses periodically and screaming it into their faces, and simply discontinuing sales in Louisiana where I know folk are a little ‘diffurnt’.

“But ultimately we decided the determining factor was the relative intelligence of the purchaser, not the backward brand of hick banjo music they listen to.”

Some of the questions included in Apple’s training for sales associates include:

    * Is the purchaser repeatedly jabbing pointy objects such as knitting needles into his or her eyes?
    * Is the purchaser drooling openly or slurping noisily from a juice box?
    * Is the purchaser wearing any combination of the following items: rainbow suspenders, flood pants, a pork pie hat, a button that says “Kiss me, I’m [anything]!”, a flounder or other fish, lederhosen (pending the opening of the Apple Store Stüttgart).

Cook said that the change is not expected to effect Apple’s revenue figures substantially as most stupid people also tend to be tasteless as well, and are therefore more likely to already be Windows users.

[michael.conner]

An experimental build can be gotten here:
ipod5g-64MB

This is a build of the 2006-05-25 23:45 CVS source with only the fix to allow the use of 64MB. It has no other patches applied.

Needless to say, its *only* for a 5th gen ipod with 64MB memory (ie 60Gig ipod video).

If anyone has any problems with it let me know.

I've used it for several hours so far without any problems.

I just installed it on mine.   Nice work!   Once the buffer filled up with an album, I was able to skip from track to track -- all the way to the next-to-last song -- without it accessing the disk.  This will seriously do wonders for the battery life!

[Murmur2k]

Can we get support for the 64 meg cache instead of 32 on 5g 60gig?

Just a quick update. It appears I have 64 MB working. The changes to get it working are:

tools/configure: set memory=64

and

firmware/crt0.S: change line 72:
mov    r1, #0x3a00
to
mov    r1, #0x7400

I believe this tells the memory controller how much memory (in pages?) to remap.

I'll post a little later with a build.

Orfax - when do you do the set memory=64 bit? do you run ../tools/configure then select N still?
Thanks

[orfax]

Orfax - when do you do the set memory=64 bit? do you run ../tools/configure then select N still?
Thanks

Modify the configure script and crt0.S before running "../tools/configure", and then build as you normally would (ie select 15 and then select N).

If you want to rebuild another version with a different memory allocation, you will have to remove the build directory, and start all over.

Has anyone using this build/patch notice any significant differences/benefits?

I'll get a better idea when I get back to work (which is where I use my iPod). Though I've only just bought it, and I haven't even run down the battery all the way yet (so I'm probably not a good judge).

[mrmagic526]

The main reason 64mb isn't used right now is that we don't have a way of detecting if there's 32 or 64mb on the device

I'm assuming there's a way to determine how large of a hard drive is in the unit.  You could use that.  Have it detect that and then for the 60 gig have it use 64 meg and if it find s a 30 gig hard drive have it use 32.  Just a random thought.

Magicman

[Llorean]

They're working on a better way to detect RAM, because it's possible that future device (and 80gig 5G?) will happen, and it'd be better not to depend on HD size. Especially since if a good method is determined, one could use it for other targets that may have multiple RAM sizes, if I understand.