Activity for jimmy zhang
-
jimmy zhang posted a comment on discussion Open Discussion
yes, why?
-
Thanks very much for your inputs and help!! Bochs is a great piece of software, and I am grateful that this project is run by awesome people like you!!
-
DOR's bit field definition says that bit #3, if set to 1, enables IRQ and DMA (on the 82077AA spec sheet), it says IRQ is enabled, DMA monitoring pin , Terminal count.. so there is a bit of ambiguity here vs OS dev site... if the sense input is indeed needed, should i do it 4 times if polling mode is automatic??
-
I found that indeed I need to sense input after fdc reset. I do not have to sense the interrupt status after floppy reset because I am in the DMA mode, not polling mode... After reading the documentation on osdev, I think there is error ambiguity in the article. below is from OS dev Sense Interrupt This command's main function is to return any error code from a Seek or Recalibrate command to your driver. It also clears an internal bitflag in the controller. It is required in three circumstances that...
-
I do not have to sense the interrupt status after floppy reset because I am in the DMA mode, not polling mode... below is from OS dev Sense Interrupt This command's main function is to return any error code from a Seek or Recalibrate command to your driver. It also clears an internal bitflag in the controller. It is required in three circumstances that produce interrupts. After doing a Controller Reset procedure with drive polling mode turned on. After the completion of a Seek command (or Relative...
-
I have tried to reset fdc twice, both times triggered the interrupt, no interrupt is triggered by recalibrate. I have tried to recalibrate without floppy reset, I got the interrupt!!!
-
I have tried to reset fdc twice, both times triggered the interrupt, no interrupt is triggered by recalibrate
-
I created a compressed zip file that contains everything I got with my OS, if you have a linux machine, just have to run the bochs script... to do that 1. unzip 2. cd into the directory that is generated by the unzip command 3. run this single command (cd src; make clean; make all); ./update_image.sh; ./run_bochs.sh
-
I created a compressed zip file that contains everything I got with my OS, if you have a linux machine, just have to run the bochs script... to do that 1. unzip 2. cd into the directory that is generated into the unzip command 3. run this single command (cd src; make clean; make all); ./update_image.sh; ./run_bochs.sh
-
ok, my toy OS has 2 floppy, both 1.44mb, I am trying to initialize the second one...which is formatted as fat12. Now DOR's last 2 bits selects the drive.. so the DOR should be set to 0x0d (dma 1, reset 1, dsel 1) write 0 to DOR then write 0x0d to it, I received the first interrupt.. there are a couple of things like setting data rate and specify the step rate and head unload/load now I can turn on the motor by writing 0x2d to 0x3f2 (DOR), wait for 500ms, then I issue command recalibrate , first input...
-
ok, my toy OS has 2 floppy, both 1.44mb, I am trying to initialize the second one...which is formatted as fat12. Now DOR's last 2 bits selects the drive.. so the DOR should be set to 0x0d (dma 1, reset 1, dsel 1) write 0 to DOR then write 0x0d to it, I received the first interrupt.. there are a couple of things like setting data rate and specify the step rate and head unload/load now I can turn on the motor by writing 0x2d to 0x3f2 (DOR), wait for 500ms, then I issue command recalibrate , first input...
-
floppy recalibrate not getting interrupt
-
n the init_floppy routine, trying to re-calibrate... I am using the first drive... so I send the cmd and drive # to the FDC, got stuck in the infinite loop that is supposed to exit upon irq6 interrupt... what could go wrong here? I have made a few checks. eflag's irq enable bit is on... also the previous times the interrupt and irq routine works... (as I reset FDC by writing a zero to DOR)... any suggestions?? My code snippet below, I got stuck in the while loop Code: int st0, cy1; floppy_motor(1);...
-
this is a bug that is /will be fixed...you can fix it yourself... it was a wrong decision to make it static
-
It will be fixed in the next release!!
-
Java AutoPilot default namespace searches return additional incorrect nodes
-
are you using vtd-xml standard or extended vtd-xml?
-
Can you be more specific on what went wrong or unexpected?
-
Sorry I may have misunderstood your question... to access mixed content huge CDATA text... you may want to resort to XPath or an otherwise little-known class called TextIter() it is part of the VTD-XML api... This class iterates through all text nodes of an element. VTDNav has getText() which is inadequate for mixed content style of XML. text nodes include character_data and CDATA. Since version 2.8, selectText(), selectComment(), and selectPI() were added ... you can basically instantiate the class......
-
you won't need to worry about this in XPath since 2.13... there is a new method that handles mixed content XPath according to the spex you could use a new method called getXPathStringVal(). Could you take a look and let me know what you think?
-
you could use a new method called getXPathStringVal(). Could you take a look and let me know what you think?
-
problem parsing xml document with unicode characters past U10000
-
this bug is marked as fixed
-
Issue when parsing CDATA
-
Single Quote is throwing error
-
I am closing this issue... let me know if you need more assistance
-
ok.. this is actually not a bug... vtd will break CDATA or char data longer than 1MB into multiple tokens of maximum 1MB each... and when you call toString()... VTD will automatically assemble those tokens back into the one of desired length.. the problem now is that you are calling toString on the first token (which already assembles teh entire string for you), then you move on to the next token and merge with the string representation of the second token (which could include the third or fourth...
-
Unexpected result reading node text from a Base64 CDATA value
-
Thanks! will look into it and get back
-
It is now on maven central. fyi
-
Do you know how to do it? I will try my best but I need to investigate.
-
download 2.13_4 and you will find the fix
-
can you isolate the issue and put together a test case for me... I be glad to take a look for you
-
Sorry for the late reply. Union xpath absolutely work in vtd-xml... I have tested this thoroughly
-
hapreet can you elaborate on the problem you are having or is it related to leena's issue?
-
you can't have single quote in an xpath expression...it is syntactically correct!
-
have you switched to 2.13.1 and this problem might have been solved...
-
Good point... thanks for the input.
-
it is being fixed, patch or new release will go out soon.
-
yes this bug is now fixed... check out the latest vtdGen.java
-
ArrayIndexOutOfBoundException in multithread environment with version 2.13
-
evalXPathToString() is not working in AutoPilotHuge
-
I will close this thread
-
one more thing: make sure the # of threads is <= than the number of physical cores....
-
I got 65ms on my machine running your code
-
ask your boss to get you a new machine... I got sub 1ms on average in query perf...
-
ask your boss to get you a new machine... I got sub 1ms on average in query perf...
-
1 lakh records ? what is lakh? ap.evalXPath() taking much more time? no way... you...
-
also try to use evalXPath before anything else.... do this if (ap.evalXPath()!=-1)...
-
again, I need a solid test case... a code piece without dependency on spring would...
-
yes, if you change your xpath to /data-set/record[COL1='" + i + "' and COL2='1' and...
-
do you understand my previous message explaining why u are getting empty strings...
-
I need you to isolate the error, get rid of spring framework dependency and simplify...
-
when you call evalXPathToString(). are you aware what you are supposed to get? also...
-
I can come up with a performance related patch, from 80ms to much lower... if the...
-
The reason you get empty space printed out as output is because in extended VTD implementation,...
-
ok, I tried your code with standard vtd-xml to test the performance, it took about...
-
your input this time is less helpful... it doesn't give enough detail... I want to...
-
Your code has one issue that causes the problem, the fix is super simple.... you...
-
Your code has one issue that causes the problem, the fix is super simple.... you...
-
Your code has one issue that causes the problem, the fix is super simple.... public...
-
Your code has one issue that causes the problem, the fix is super simple.... public...
-
ArrayIndexOutOfBoundException in multithread environment with version 2.13
-
ok, will look into it.. thanks for reporting
-
this is a bug that has been idnentified and corrected in 2.13.1... I am embarassed...
-
xpath expressions containing the != operator are not evaluated correctly in 2.12 & 2.13
-
I mark this ticket closed for now...
-
all the bugs plus a few more are now being released in to 2.13_1....
-
I have checked in 2 files that you need to check out for a rebuild.. the first one...
-
xpath expressions containing the != operator are not evaluated correctly in 2.12 & 2.13
-
yes, thanks this problem is positively identified... my bad... I slapped myself on...
-
Actually I am referencing to the CVS repo on sourceforge http://vtd-xml.cvs.sourceforge.net/viewvc/vtd-xml/ximple-dev/com/ximpleware/extended/VTDNavHuge.java?view=log...
-
ArrayIndexOutOfBoundsException with getContentFragment
-
This bug is caused by an bug that was fixed in standard edition but not in the extended...
-
ArrayIndexOutOfBoundsException with getContentFragment
-
Thanks! will look into it and get back
-
that particular char is outside the range of chars supportable by java's internal...
-
ok, will look into it and get back
-
good point, will look into that... in the meaning time, 2.13 is a big step forward...
-
VTDGen should support reading from streams, not just files
-
Issue with Autopilot and multithreading
-
Java AutoPilot default namespace searches return additional incorrect nodes
-
Can you do a build yourself with the update vtdNav.java? The URL below... http:/...
-
vtd-xml 2.12 onward has a change in the behavior of matchElement() for VTDNav. based...
-
The key issue with vtd-xml is that it is not a stream based parser, it is instead...
-
The key issue with vtd-xml is that it is not a stream based parser, it is instead...
-
Yes, this is indeed a bug like you described and it is fixed in 2.12 and 2.13
-
Please use stackoverflow.com as the primary destination for vtd-xml related issu...
-
Most of the q&a and support activities have moved to stackoverflow.com, using the...
-
yes, it is, it is a known issue with c C#, ... will fix soon, also plz use stackoverflow...
-
Can u send me a zip file with all the test cases? or can u email me jzhang@ximpl...
-
Can u send me a zip file with all the test cases?
-
hi, I think this is a known bug that has been fixed...
-
I think this is a bug that has been fixed in v2.11, can you verify?
-
we are working on C/C++ port fyi,
-
HI, Variable declaration works as far as I know. I think xpath2.0 have some fundamental...
-
Can you please submit a test case?
-
2.12 will come out soon, in the mean time go to cvs to get vtdNav.java
-
I believe this is a bug that may have been reported and fixed, can you download version...
-
cvs only, so i am old school :(
1 >