|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: BD Drive Enable buffer write with sg_raw [message #632 is a reply to message #631] |
Sun, 12 February 2012 13:00   |
glevand
Messages: 955
Registered: July 2011
Location: SONY
|
Gitbrew God |
|
|
Hmm, interesting.
Before enabling buffer write:
glevand@debian:~$ sudo ./bd_mode_sense -p 0x2d | hexdump -C
00000000 00 0e 00 00 00 00 00 00 2d 06 00 00 00 00 00 00 |........-.......|
00000010
Enable write to buffer 4:
glevand@debian:~$ sudo ./bd_enable_buffer_write -b 4
After enabling buffer writing:
glevand@debian:~$ sudo ./bd_mode_sense -p 0x2d | hexdump -C
00000000 00 0e 00 00 00 00 00 00 2d 06 04 00 00 00 00 00 |........-.......|
00000010 [Updated on: Sun, 12 February 2012 13:09] Report message to a moderator |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: BD Drive Enable buffer write with sg_raw [message #638 is a reply to message #519] |
Sun, 12 February 2012 15:40 |
Mark Webber
Messages: 20
Registered: February 2012
Location: Australia
|
Gitbrew Noob |
|
|
Ok, just checked what page 0x2d was doing since 0x2f was not changing.
It changes from "2d 06 00" to "2d 06 04" after using enable_write_buffer
Edit: My bad, just realised I was checking the wrong page (0x2f) when I first replied.
When checking 0x2d, it changes to whatever buffer I have told to enable writing to.
I still have the same status after trying to write though.
2/0/8
What command did you use to dump the buffer to a file with?
It could be the file I am using (bin file) that is causing the probelms.
[Updated on: Sun, 12 February 2012 15:52] Report message to a moderator |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: BD Drive Enable buffer write with sg_raw [message #657 is a reply to message #656] |
Thu, 16 February 2012 04:20 |
Mark Webber
Messages: 20
Registered: February 2012
Location: Australia
|
Gitbrew Noob |
|
|
Could it be that it is expecting a full MKB to extract the info from itself?
Possibly wrting a new HRL directly also causes the drive to expect new AACS keys etc as well since it would be seen by the drve firmware as an update.
When I was messing with the MX and SPI flasher, erasing all the info from 0xE000 on caused the drive to update not only the HRL, but also AACS keys.
Lv2diag would check the drive HRL, then check its own (v1) then if a disc was present check that also. This seems to only be true if the Lv2diag HRL was higher (anything is higher the nothing of course) would it check the disc.
If the drive HRL was higher then the V1 HRL in Lv2diag, it would ignore the disc and carry on.
Edit: In theory all that should be required would be to change the byte that defines the HRL verison to 0x00.
Then Lv2diag should behave as above and overwrite all the info with the new AACS keys and correct HRL from the disc.
[Updated on: Thu, 16 February 2012 04:24] Report message to a moderator |
|
|
|
| Re: BD Drive Enable buffer write with sg_raw [message #658 is a reply to message #657] |
Thu, 16 February 2012 18:29 |
glevand
Messages: 955
Registered: July 2011
Location: SONY
|
Gitbrew God |
|
|
|
I don't think so. because if you take a look at lv2diag you will see that after it has written buffer , it immedietly reads the same buffer back with SCSI READ BUFFER and compares the read data with the data which was written. ANd if it doesn't match then it exits with an error.
|
|
|
|
Official Gitbrew Forums
Members
Search
Help
Register
Login
Home
