Rockbox General > Rockbox General Discussion

new ipods - rockbox port proposal

<< < (9/26) > >>

Bugsy:

--- Quote from: LambdaCalculus379 on September 06, 2007, 12:56:20 AM ---
--- Quote from: Chronon on September 05, 2007, 04:03:39 PM ---You should ask if you can try out a scanner.  Then rip it open then and there!  

--- End quote ---

Oh man, those Apple Store employees would scream in agony if I did that! ;D

/me uses Angry Voice "I AM LRRR OF THE PLANET ROCKBOXIA! TREMBLE IN FEAR AS I PORT ROCKBOX TO YOUR PUNY NEW IPODS!! BWA HA HA HAAA!!"

--- End quote ---

Hahahahahahahahaha.  :D

I just fell out of my chair because of this one.

You are now quoted on facebook.

I was already planning to buy the 80gb next week anyways, so cheers to Apple for this one.

But without Rockbox, the 160gb is useless. So i'm in a pickle.

Any estimates on how much time it takes to learn whatever you need to program the ipod for rockbox?  :P

LambdaCalculus:
When we're flying blind like we are with the nano, let's just say... "Only time can tell."

We never have an estimate as to when a port will be done. It's ready when it's ready, and that's also why there's no such thing as release dates in the open source community.

AlexP:
http://www.rockbox.org/twiki/bin/view/Main/NewPort

You will also probably be working on hardware without datasheets and very strong encryption.

peterw:
If we're lucky, Walrus is right and the iPod Classic is basically a 5.5g. If so, the Classic 80 and 160 shouldn't be too hard to support (says a guy who's barely compiled Rockbox source).

But the iPod Touch? The Rockbox code is largely driven by hardware button & switch events. The iPod Touch has what, one button (home) and one switch (hold)? Making Rockbox work on the iPod Touch would mean dealing with some serious user input issues: interpreting screen input, and possibly drawing controls on-screen. Even if you put aside the possibility any effort required to get code to run on the iPod Touch, the UI issues could be huge. Easiest might be claiming some portion of the screen for permanent user input control space. But would users be happy with a portion of the screen permanently dedicated to user input?

I hope the Classics are easy to support. I don't like the wheel much, but there's a lot to recommend the larger iPods for large music collections (which is why I've got a 5.5g 80gb). With all my decent quality MP3s and all of English Wikipedia on my iPod (http://www.rockbox.org/tracker/task/4755), I can't imagine using a DAP with only 16gb.

Hopefully the Classics' arrival will mean good prices on the 5.5g Videos soon...

-Peter

gnychis:
heres an interesting proposal, ripping the hard drive out of the 160gb and dropping it in the 5.5G 80gb body.  Maybe this is possible.  If you check the sizes of the 6G and 5.5G 80 and 160 ipods, the 6th gen is .02mm thinner... this is a very small difference.

It seems as though Toshiba just announced a mini 160gb drive... that many are *speculating* may be the drive in the 6th gens:
http://www.engadget.com/2007/09/06/toshiba-announces-ipod-classic-sized-80gb-and-160gb-1-8-inch-dis/

So to avoid needing to crack the 6 gen just to get the 160gb, maybe it could be possible for us to drop a new drive in.

- George

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version