Good to see some interest in this still :)
Do we need to set some bit to enable Jazelle?
No, the ARM people like to have special instructions to change
processor modes, like ENTERX or BXJ or the like. (I think. :))
No, we do have to explicitly setup Jazelle mode (IMHO).
I stumbled upon
Thank you for the links, these are things I've not seen before.
So let me dump the stuff I turned up so far:
URL: http://www.scratchpost.org/patches/jazelle-disassembly.png
Here you can see the size and alignment of the java instructions.
(the entire document is
Hi,
sorry for chiming in, incidentally I've just started to study the arm
architecture and the ARM1136J-S manual seems clear about a couple of
things
On 8/15/07, Simon Pickering [EMAIL PROTECTED] wrote:
Thank you for the links, these are things I've not seen before.
So let me dump the stuff I
Hi,
great to see someone tinkering with jazelle.
So let me dump the stuff I turned up so far:
URL: http://www.scratchpost.org/patches/jazelle-disassembly.png
Here you can see the size and alignment of the java instructions.
(the entire document is
Hello all.
My apologies this is going to be a long one...
All the code mentioned in this email can be found under this directory:
http://people.bath.ac.uk/enpsgp/nokia770/jazelle/
After reading the patent I wrote a piece of code to test whether Jazelle works,
as Scott Bambrough suggested. The
Hi Larry,
A couple thoughts from a former hardware hacker here: first, serial
ports are your friend so if you can find a sacrificial device that has
a cracked screen or some other serious but non- life-threatening
defect you should probably invest in a level-shifter chip and a DB-9
On Wed, 2007-07-18 at 11:01 +0100, ext Simon Pickering wrote:
Yes, in an ideal world this would be nice, but I'm doing okay with ssh/sftp
over
wifi for the time being. Out of interest, does the N800 actually have solder
points for a serial port at some known location?
There are websites,
A couple thoughts from a former hardware hacker here: first, serial
ports are your friend so if you can find a sacrificial device that has
a cracked screen or some other serious but non- life-threatening
defect you should probably invest in a level-shifter chip and a DB-9
connector (and some
]
An: 'Larry Battraw' [EMAIL PROTECTED]
Cc: maemo-developers@maemo.org
Gesendet: Mi., 18. Jul. 2007 12:01:23 CEST
Betreff: RE: Java acceleration/Jazelle
...
Does anyone know whether there are there any good docs/books on ARM asm
programming, telling people these sort of things? This is an interesting
Simon Pickering wrote:
The second thought is learn the ABI convention for calling C methods
from assembly and you can pass whatever data you need to a function
that will do the printing for you. I'd suggest going with this route
since it will be the most straightforward without soldering
On Wednesday 18 July 2007 13:01, Simon Pickering wrote:
Does anyone know whether there are there any good docs/books on ARM asm
programming, telling people these sort of things? This is an interesting
(and hopefully useful) learning experience, but can be really frustrating
when I know what I
Hi Siarhei,
Does anyone know whether there are there any good docs/books on ARM asm
programming, telling people these sort of things? This is an interesting
(and hopefully useful) learning experience, but can be really frustrating
when I know what I want to do, and pretty much how to, but not
I've adjusted the code I wrote to test Scott Bambrough's suggestion
(see earlier in the thread). The name and URL is still the same:
http://people.bath.ac.uk/enpsgp/nokia770/jazelle/test_jazelle7.c
After the code starts and BXJ R12 is issued, the code does branch to
the handler whose address
Folks,
This is a summary of a conversation Simon and I had off line. We
decided it would be a good idea to post it here to the list so others
could see the discussion and comment. A couple of caveat's to keep in
mind. I haven't had a chance to compile and try the code yet, I've been
reading
Hi Scott ( all),
The following describes an experiment I suggested:
Create an array with opcodes 204 to 255 in it. Create one handler for
all opcodes.
Set up R14 to point to opcode 204.
Set up R12 to your handler.
Push the address you want to return to onto the stack.
Write your handler
On 7/17/07, Simon Pickering [EMAIL PROTECTED] wrote:
Hi Scott ( all),
The following describes an experiment I suggested:
Create an array with opcodes 204 to 255 in it. Create one handler for
all opcodes.
Set up R14 to point to opcode 204.
(snip)
I sat down and wrote a bit of code that
Did you make a typo in your declaration (on p34) of int code[]? Should
this not be unsigned char code[] as bytecodes are 1x byte not n x byte
long (I'm assuming you're running on a machine with sizeof(int)1)?
This is not a typo. I don't understand the reason, but it had only
worked with the
Hi all,
Sebastian, in this link:
You can find a small example in my jalimo slides from linuxtag2007
(slide 33ff).
http://www.jalimo.org/wiki/doku.php?id=news:linuxtag2007
(direct link:
http://www.jalimo.org/documents/jalimo-slides_english_linuxtag2007.pdf)
Did you make a typo in your
Not such good news.
I have learned alot about extended inline asm though.
Anyway, my final code is here:
http://people.bath.ac.uk/enpsgp/nokia770/jazelle/jazelle1.c
It's changed a fair bit from my first untested code and should now work
as planned. Unfortunately what happens is a segfault. So
Ah, looks like I spoke too soon.
My original branching code seems to have been misguided, hence the segfaults.
New improved code here:
http://people.bath.ac.uk/enpsgp/nokia770/jazelle/jazelle5.c
Now, when I call bxj r12, with r12 pointing to the handler code and r14
pointing to the Java code
New improved code here:
http://people.bath.ac.uk/enpsgp/nokia770/jazelle/jazelle5.c
Sorry, wrong file name, it should be
http://people.bath.ac.uk/enpsgp/nokia770/jazelle/test_jazelle5.c
Simon
___
maemo-developers mailing list
Hi Simon,
sincerely I don't found the time to test your code yet.
Did you make a typo in your declaration (on p34) of int code[]? Should
this not be unsigned char code[] as bytecodes are 1x byte not n x byte
long (I'm assuming you're running on a machine with sizeof(int)1)?
This is not a
Sebastian Mancke schrieb:
Hi Simon,
sincerely I don't found the time to test your code yet.
Did you make a typo in your declaration (on p34) of int code[]? Should
this not be unsigned char code[] as bytecodes are 1x byte not n x byte
long (I'm assuming you're running on a machine with
Hi Sebastian,
nice research !!! This seams easier (and more os independent) than my
thoughts with an interrupt in kernel mode. Although we can not say for
sure, that Jazelle is implemented the way, the patent describes, this is
a very good point to get a forthcome.
Thanks. I had also been
Hi all,
If this is all already known please let me know and I'll stop waffling,
but some Googling couldn't find anything, so I'll present what I've
found thus far.
I had a look around for some more information and found the patent
for Jazelle: US patent number 7089539.
Google link here
Hi Simon,
nice research !!! This seams easier (and more os independent) than my
thoughts with an interrupt in kernel mode. Although we can not say for
sure, that Jazelle is implemented the way, the patent describes, this is
a very good point to get a forthcome.
Regards,
Sebastian
Simon
The next question is how to implement the undefined instruction
exception handler. Is 0x0004 (or optionally 0x0004) writable (I
need to write some test code really) from a user program? Assuming it
is, then it should be reasonably straightforward to write an exception
handler and to
On Sat, 30 Jun 2007 23:36:23 +0100
Simon Pickering [EMAIL PROTECTED] wrote:
The next question is how to implement the undefined instruction
exception handler. Is 0x0004 (or optionally 0x0004) writable (I
need to write some test code really) from a user program? Assuming it
is, then
28 matches
Mail list logo
