HD Homebrew Project Developement (Old Thread)

[endy]

Frankly, who cares.

There is still far too much work left on the program core before anybody starts asking 'can it do this', 'how about adding this', etc.

This topic is getting far too polluted with trash, and Krevnik appears to be missing in action

[dlanor]

Frankly, who cares.

There is still far too much work left on the program core before anybody starts asking 'can it do this', 'how about adding this', etc.

Indeed! I agree completely.
I suggest that we stockpile our more exotic ideas for later, rather than posting them here now. Once basic functionality has been achieved we can revive discussion of things to add or modify.

This topic is getting far too polluted with trash,

True, but on a subject like this it's hard to avoid, especially if it starts attracting the newbies too...

I suggest the following guideline for this thread:
----------------------------------------------
This thread was created to discuss Krevnik's "HD Homebrew project", just like it says in the thread title. So lets stop discussing ToxicOS, PS2 emulators, and other unrelated stuff here. Even if they do contain some functionality similar to what we want, this is going to be a new design, not just a ripoff.

Don't get me wrong now. Of course it would be ok to discuss how others solved something when this project runs into some problem, so that new insights gained from the other solutions can inspire some new solution. But that need is not here yet, so save it for later.

and Krevnik appears to be missing in action

Let's hope it's 'Busy in action' instead
I just checked, and it's been a week since his last post here. That may be more than some of us like, but no real cause for alarm.

Best regards: dlanor

[Krevnik]

Yes, I have been rather busy lately, with not much time, I could have sworn I made a post saying that it would get rather busy for me... but I guess I didn't. Anyways, since I recently graduated from college, I am also in the middle of a job hunt, and because my degree doesn't cover C#/.NET development, I am also making sure I am up to snuff on that as well. In short, I have two large-scale projects being worked on, and a job hunt. This means that every so often I just won't have the time to post updates... One of the reasons why contributions are very welcome.

To those who have been reverse engineering: Good work so far, since I got rather busy and seem unable to extract the code from the webpage (some weird thing about IFRAME tags garbling the ability to copy/paste on my machine), could you guys e-mail me the work done so far in a text format?

I hope to get back to work on this for awhile next week, as I have been working out how the heck to handle partition creation/etc through ps2atad and libhdd, and how to do raw access of the hdd through the hdd0: device.

[cmal1492]

krevnik - I stubled across this:

The first one will be the uncruncher stub. By default, it's
a zlib stub compiled to be loaded at 0x88000. You may want to compile other
stubs, to get different loading addresses. I provide another stub which loads
at 0x1a00000. Should you produce new stubs, just change the stub/Makefile.
The second section contains the packed data. This basically can be loaded
anywhere. That is the "base" option of the command line.

In the ps2packer 0.2 readme, not sure if that has much relevance to hdl having something at 0x88000 - unless it is the decrypt/decompression stub perhaps?

[ps2feen]

i jsut boguht C++ for dummies.. im gona read the hole thing and hopefully know what your talking about

[Krevnik]

HDL uses 0x88000 for the patching software, which catches the IOP reset, and depending on which version (since the team has done some work to improve HDL as part of Toxic) 'patches' the IOP modules.

And all I have to say about this last week is: Grr.

Things started good, and then /wham/ I get scheduled for *6* interviews out of the blue early in the week, and I am still wading through them all. However, there is a silver lining, I have gotten an offer, will have a little time for some HDDemolisher work between Tuesday and Friday of next week (after the interviews all die out and I give my response to the offer), have some time to go to a Con next weekend, and then head out to work in 10 days. Although what I am kinda thinking, is that a dev blog should be setup for this project, so we can have a place where I can rant about progress, and have some discussion on the various problems. Would this interest those following the development, and those who might be interested in contributing bits and pieces?

[lazyj]

I think a blog would be great, if not just for ppl like me who are interested in the progress you guys are making

I think its awesome that this is open source.

[Kiyo]

HDL uses 0x88000 for the patching software, which catches the IOP reset, and depending on which version (since the team has done some work to improve HDL as part of Toxic) 'patches' the IOP modules.

And all I have to say about this last week is: Grr.

Things started good, and then /wham/ I get scheduled for *6* interviews out of the blue early in the week, and I am still wading through them all. However, there is a silver lining, I have gotten an offer, will have a little time for some HDDemolisher work between Tuesday and Friday of next week (after the interviews all die out and I give my response to the offer), have some time to go to a Con next weekend, and then head out to work in 10 days. Although what I am kinda thinking, is that a dev blog should be setup for this project, so we can have a place where I can rant about progress, and have some discussion on the various problems. Would this interest those following the development, and those who might be interested in contributing bits and pieces?

i can offering you some host in asia if wants. maybe use wiki?

[DJFire]

<-- This Is My First Post Here

I Have Webspace You Can Borrow
--1 Gig Space
--1 Terabyte transfer a month
With All The Fancy Features MySQL, PHP, Ect...

[romz]

I need some help again. Code (below) can be found in "cdvdman" modules and I have problem to reconstruct it in "C" code.

          addui      $sp, -0x18
          lui          $v1, 0x38E3
          sw         $ra, 0x18+ra($sp)
          lw          $v0, SysClock.low($a0)
          ori         $v1, 0x8E39
          multu     $v0, $v1
          la          $a0, 0xC744
          mfhi       $a2
          ja          Kprintf
          srl         $a1, $a2, 13

What source can cause compiler to generate such code? It's definatelty something like

Kprintf("bla bla bla %d\n", arg0.low /* ??? */);

I suspect it's an optimized code for some divide operation.