Bueno segun he leido por ahi... parece que estos dos amigos de la scene se han unido de manera q Graf_Chokolo esta ayudando a Flukes1 con el LV1&2.
Aqui podemos ver un mail que envió Graf_Chokolo a Flukes1:
You don’t need lv1 peek and poke, i do not use lv1 peek and poke, i just map HV memory address into GameOS LPAR with read/write rights. I used lv1_undocumented_:function_114, just one byte must be patched in this HV call and after that you can use it to map any memory address into GameOS LPAR with Read/Write protection.
Look at my HV reversing page, i explaided there how to use this HV call.
O lo que se viene llamando en español:
Tu no nesecitas el LV1 peek and poke,yo no uso el lv1 peek and poko,acabo de mapear las direcciones de memoria en HV GameOS LPAR con lectura / escritura de los derechos.Yo uso lv1_undocumented_:function_114,sólo un byte debe ser corregido en la presente HV call y después de eso se puede utilizar para asignar cualquier dirección de memoria en GameOS LPAR con lectura / escritura de protección.
Mira en mi pagina HV reversing ,ahi explico cómo utilizar esta llamada de alta tensión.
Ademas tenemos este registro del chat...
<
@flukes1> graf just hinted a way to patch lv1 for full r/w access in lv2
<
@flukes1> once we got that working, we dump lv1 RAM
<
@flukes1> search for lv2 hash
<
@flukes1> and find the hash code
<
@flukes1> im patching lv1 now to allow us to edit it via lv2
< +mastag22> so you are keeping lv2 and lv1 patched then
< +mastag22> but you are using an lv1 call to enable it?
<
@flukes1> eh?
< +mastag22> im confused
< +mastag22> or are you patching lv2 commands INTO lv1
< +mastag22> and calling them from lv1
<
@flukes1> no
<
@flukes1> we are patching the equivalent of peek/poke into lv1
<
@flukes1> its not actually peek poke but it allows us to do exactly what peek/poke does
<
@flukes1> and we are keeping our peek/poke patch in lv2
<
@flukes1> we can then make an app to write a syscall to lv2 in memory
<
@flukes1> which will call the peek/poke-similar thing in lv1
<
@flukes1> and pass the result back down to our app running in gameos
<
@flukes1> which will use it to dump lv1
En fin... ya veremos como acaba todo esto. Esperemos q con la demanda de sony no se retrase este tema.