|
|
02-17-2010
|
#41 |
|
Senior Member
 
Join Date: Jan 2008
Location: Lisbon, Portugal
Posts: 6,681
Likes: 2,087
Liked 2,449 Times in 1,389 Posts
Mentioned: 138 Post(s)
Tagged: 0 Thread(s)
|
Not sure, i guess thats a path to the driver but can it be extracted?? what lv is this 0,1,2?
Only this is not enough at least for me... maybe Dissane can tell us more.
__________________
<eussNL> judge: ´so why did you torrent 5 million AVI of women moaning´ <eussNL> <TizzyT> i dont judge if it sounds good i listen |
|
|
|
02-17-2010
|
#42 | |
|
Member
 Join Date: Jul 2008
Location: Austria
Posts: 121
Likes: 18
Liked 85 Times in 29 Posts
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
I don't think the drivers can be extracted since the they`re not installed (or at least the necessary drivers for the RSX is not provided for the PS3 on Linux). Also we can't even address the frame buffer (w/o a hack). This means zero support for any RSX goodies or maybe not... If I'm correct. According to the memory dumb lv1 is looking for the RSX driver's source code. Well I can see a "device.h" header file there. When the Hypervisor realizes that the source file is not there it stops checking for any other source files. We really need those Zego drivers to figure this out. I'm pretty sure the Zego drivers solely just won't be enough but from there on things would become easier. Modifying the drivers to work with the PS3 shouldn't be as challenging as finding a hole on the Hypervisor. Maybe I'm right maybe I'm wrong. Who knows... |
|
|
|
|
|
Likes: (1) |
 |
| Bookmarks |
| Thread Tools | |
|
|
