[syslinux] Syslinux 4.10-pre20

Sat May 26 02:32:07 PDT 2012

Sir, your keyboard code is not working on my system you better you this code

PortWait proc a_type:dword

;A read from port 64H gives the following status byte:
;
;   Bit     Function
;    7      1 = Parity error
;    6      1 = General Time Out
;    5      1 = Auxiliary output buffer full
;    4      1 = Inhibit switch
;    3      1 = Command/data
;    2      1 = System flag
;    1      1 = Input buffer full
;    0      1 = Output buffer full
cli
.if a_type==WAIT_READ
wait_type_0:
in al,64h
bt ax,6
jc error
bt ax,7
jc error
bt ax,WAIT_READ; if bit 3 set data is available at 64h
jnc wait_type_0
xor eax,eax
.elseif a_type==WAIT_WRITE
wait_type_1:; Bit 1 should be zero before we able to send command
in al,64h
bt ax,6
jc error
bt ax,7
jc error
bt ax,WAIT_WRITE
jc wait_type_1
xor eax,eax
.elseif a_type==WAIT_COMMAND
wait_type_2:; Bit 0 and 1 should be zero before we able to send command
in al,64h
bt ax,6
jc error
bt ax,7
jc error
bt ax,WAIT_COMMAND
jc wait_type_2
xor eax,eax
.elseif a_type==WAIT_READ60
wait_type_4:
in al,64h
bt ax,6
jc error
bt ax,7
jc error
bt ax,WAIT_READ; if bit 3 not set data is available at 60h
jc wait_type_4
xor eax,eax
.elseif a_type==WAIT_OUTPUT
wait_type_5:
in al,64h
bt ax,6
jc error
bt ax,7
jc error
bt ax,WAIT_OUTPUT; if bit 3 set data is available at 64h
jnc wait_type_5
xor eax,eax
.endif

error:
sti
ret
PortWait endp

PortRead proc

invoke PortWait,WAIT_READ
in al,60h

ret
PortRead endp

PortWrite proc a_cmd:byte

invoke PortWait,WAIT_WRITE
mov al,a_cmd
out 64h,al

ret
PortWrite endp

KeyBoardRead proc
LOCAL key:byte

invoke PortWrite,0AEh
invoke PortWrite,0D2h
in al,60h
;invoke PortRead
;mov key,al
;invoke PortWrite,0AEh
;mov al,key
;push eax
;push eax
;invoke dw2bin,eax,base_buffer
;invoke Print,base_buffer
;pop eax
;invoke dw2hex,eax,base_buffer
;invoke Print,base_buffer
;invoke PrintRel,addr crg
;pop eax
;invoke PortWrite,0A7h
ret
KeyBoardRead endp 

________________________________
 From: H. Peter Anvin <hpa at zytor.com>
To: For discussion of Syslinux and tftp-hpa <syslinux at zytor.com> 
Cc: Geert Stappers <stappers at stappers.nl> 
Sent: Saturday, May 26, 2012 6:04 AM
Subject: Re: [syslinux] Syslinux 4.10-pre20

On 05/25/2012 03:50 AM, Geert Stappers wrote:
> On Thu, May 10, 2012 at 11:04:00PM -0700, Shantanu Gadgil wrote:
>>
>> Hi,
>> Any update on this? Does the traffic dump help?
>> Is it even correct? (I am not familiar with using tcpdump much)
> 
> Both tcpdumps could be further analyzed. So kno
> 
> The v406pre3.dump looks fine.
> 
> The v410pre20.dump his this interresting, perhaps strange pattern:
> 
> 13:29:39.210724 IP 10.209.170.241.49153 > 10.209.170.239.69:  79 RRQ "pxelinux.cfg/44454c4c-4200-1037-8038-c2c04f343253" octet tsize 0 blksize 1408 
> 13:29:39.210894 IP 10.209.170.239.40073 > 10.209.170.241.49153: UDP, length 79
> 13:29:39.212393 IP 10.209.170.241 > 10.209.170.239: ICMP 10.209.170.241 udp port 49153 unreachable, length 36
> 13:29:39.282219 IP 10.209.170.241.49153 > 10.209.170.239.69:  79 RRQ "pxelinux.cfg/44454c4c-4200-1037-8038-c2c04f343253" octet tsize 0 blksize 1408 
> 13:29:39.282329 IP 10.209.170.239.33209 > 10.209.170.241.49153: UDP, length 79
> 13:29:39.283941 IP 10.209.170.241 > 10.209.170.239: ICMP 10.209.170.241 udp port 49153 unreachable, length 36
> 13:29:39.392125 IP 10.209.170.241.49153 > 10.209.170.239.69:  79 RRQ "pxelinux.cfg/44454c4c-4200-1037-8038-c2c04f343253" octet tsize 0 blksize 1408 
> 13:29:39.392235 IP 10.209.170.239.44117 > 10.209.170.241.49153: UDP, length 79
> 13:29:39.393792 IP 10.209.170.241 > 10.209.170.239: ICMP 10.209.170.241 udp port 49153 unreachable, length 36
> 
> 
> .241:49153 asks .239:69 for file
> .239:40073 replies .241:49153 with file not found
> .241 informs .239 that it is "unreachable"
> 
> 
> To me it seems that the 4.10 pxelinux and the PXE stack on the Dell
> don't mix that well.
> 

This is a very interesting discovery.  It could be that the native PXE
BC gets control.  This might explain at least one set of problems that
we have.

The other possibility of course is that we're using the lwIP UDP
interface incorrectly (we have already had that problem once.)

    -hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

_______________________________________________
Syslinux mailing list
Submissions to Syslinux at zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.