NAND boot testing. Test 5: SOUND!!!!/Test 7: Single NBH/Serialno/tilt2 fix - Page 43

**arrrghhh** · #**421** (**permalink**) 09-29-2010, 01:09 PM

Quote:

Originally Posted by [ACL]

I was talking to wozz yesterday. Looks like he might be back soon. But still, now you see why we need a page dedicated for releases. lol.. i can start a new thread as long as someone helps me update the contents from time to time. I'm not good at that stuff and this is why wozz handled it

I don't mind taking care of the thread as well... I would just need to create the first post so I can manage it

Either way, nate seems to be checkin back fairly frequently, and since his fingers are on the pulse more than mine, he may be a better candidate

**natemcnutty** · #**422** (**permalink**) 09-29-2010, 03:47 PM

Quote:

Originally Posted by arrrghhh

I don't mind taking care of the thread as well... I would just need to create the first post so I can manage it

Either way, nate seems to be checkin back fairly frequently, and since his fingers are on the pulse more than mine, he may be a better candidate

I do check in quite regularly. One of the advantages of being a sysadmin. When you are waiting on things to copy or finish installing or whatever, you can check up on things.

Anyway, I was hoping that someone might be able to take a look at this and confirm for me that Tinboot2.S controls startup commands. To me, it looks like HW3D is only enabled for the RHOD500 (Verizon TP2).

tinboot/tinboot2.S - tinboot-linux-msm in Tinboot for linux-msm - Gitorious

I'm still messing around with compiling Tinboot, and I think the last thing I need to do is figure out whether I need to force hw3d for any of the other devices. It also looks like Wozz had the rhod500 overclocked, but the others aren't.

On the plus side, I found a couple of modules that I wasn't compiling with the regular modules, and adding support for people using a SIM card in a Sprint or Verizon phone looks like it would be pretty easy.

**arrrghhh** · #**423** (**permalink**) 09-29-2010, 04:07 PM

Good to hear! As far as the thread, one of us should probably create a new one. Again since you seem to have a better connection with development progress, you'd probably be the better choice for making said thread.

But, I certainly don't mind either - just so long as I can get some notification about updates.

**natemcnutty** · #**424** (**permalink**) 09-29-2010, 04:13 PM

Wirelessly posted (Opera/9.80 (Windows Mobile; Opera Mini/5.1.21594/20.2479; U; en) Presto/2.5.25)

Quote:

Originally Posted by arrrghhh

Good to hear! As far as the thread, one of us should probably create a new one. Again since you seem to have a better connection with development progress, you'd probably be the better choice for making said thread.

But, I certainly don't mind either - just so long as I can get some notification about updates.

I'll start up a new thread for posting builds on in a couple hours. Want to get all of the files compiled, uploaded to dropbox and all that first. I really want to make sure the tinboot stuff is all set too. Hopefully I can get feedback on whether forcing hw3d is required on all devices as I posted earlier

**natemcnutty** · #**425** (**permalink**) 09-29-2010, 07:46 PM

OK, I've got compiling tinboot down perfect since there was a lot of stuff I had to do to prep my machine for compiling it. The biggest thing now is that I have to compile referencing a model when building such as rhod500. I see that Wozz has a single NBH for all types on the main post, and I'm wondering if I the NBH file is now universal and I only need to build it using rhod500.

If that is the case, then no update is necessary for enabling 3d, but if Wozz did some magic to make a universal NBH, then I'm not sure what to do.