ROM port Ethernet adapter

Troubles with your machine? Just want to speak about the latest improvements? This is the place!

Moderators: Mug UK, Zorro 2, Greenious, spiny, Moderator Team

Galvez
Captain Atari
Captain Atari
Posts: 175
Joined: Fri Oct 19, 2007 7:49 am

Re: ROM port Ethernet adapter

Postby Galvez » Mon Apr 02, 2018 6:18 pm

Hi Xerus,

By chance czietz was testing some network driver for the ST and hit the same problem than us.
Fortunately for me he has discovered the cause of the problem and it should be fixed now.
I've attached new modules for testing. Thanks!

rtl8012st_original.zip

rtl8012st_nodelay.zip

rtl8012st_vblsplit.zip

rtl8012st_busy.zip
You do not have the required permissions to view the files attached to this post.
Last edited by Galvez on Tue Apr 03, 2018 8:19 am, edited 1 time in total.

User avatar
Xerus
Moderator
Moderator
Posts: 1231
Joined: Fri Dec 13, 2002 9:31 pm
Location: France

Re: ROM port Ethernet adapter

Postby Xerus » Tue Apr 03, 2018 4:39 am

I confirm, you are on the good way :)
All tests come from my PC:

Code: Select all

Original: ok, 50 ping  minimum = 8ms  maximum = 46ms average = 19ms
                       minimum = 13ms maximum = 43ms average = 25ms GEM
No_delay: ok, 50 ping  minimum = 07ms maximum = 36ms average = 17ms
                       minimum = 11ms maximum = 65ms average = 25ms GEM
VBL_splt: ok, 50 ping  minimum = 06ms maximum = 40ms average = 16ms
                       minimum = 06ms maximum = 35ms average = 16ms GEM
Busy: no, boot ok but no ping works.                     
                     
old 1.3:  ok 50 ping  minimum = 06ms maximum = 39ms average = 17ms
                      minimum = 07ms maximum = 38ms average = 24ms GEM

Galvez
Captain Atari
Captain Atari
Posts: 175
Joined: Fri Oct 19, 2007 7:49 am

Re: ROM port Ethernet adapter

Postby Galvez » Tue Apr 03, 2018 8:14 am

Cool! the version with the split VBL handler has similar or even better performance than version 1.3.
Just one more attempt using the BUSY interrupt in the parallel port, driver attached.
I guess you still have problems pinging from the ST, I need to look into that.
rtl8012st_busy2.zip
You do not have the required permissions to view the files attached to this post.

User avatar
Xerus
Moderator
Moderator
Posts: 1231
Joined: Fri Dec 13, 2002 9:31 pm
Location: France

Re: ROM port Ethernet adapter

Postby Xerus » Wed Apr 04, 2018 7:28 pm

It still doesn't work with busy2 driver.
However, I see the led light; probably due to ping.ttp.
No ping from the PC.
I guess you still have problems pinging from the ST, I need to look into that.

Really strange because when I put the floppy in the Falcon, ping.ttp works well.
If you can make a debug version I will send you a videolog ;)

Galvez
Captain Atari
Captain Atari
Posts: 175
Joined: Fri Oct 19, 2007 7:49 am

Re: ROM port Ethernet adapter

Postby Galvez » Sat Apr 07, 2018 7:12 am

Hi Xerus, a new test's round :-)

There is a package to debug the ping issue with a module with the vbl split interrupt and the int4.xdd module, both with debug messages enable.
The other package is the driver with the parallel port interrupt with debug messages too. Let's see what is showing us. Thanks!

rtl8012st_splitvbl_dbg.zip

rtl8012st_busy2dbg.zip
You do not have the required permissions to view the files attached to this post.

User avatar
Xerus
Moderator
Moderator
Posts: 1231
Joined: Fri Dec 13, 2002 9:31 pm
Location: France

Re: ROM port Ethernet adapter

Postby Xerus » Mon Apr 09, 2018 6:32 pm

I'm back :)
I have 2 problems:
Debug versions do not return any info ?!
Looks like normal versions.
2nd problem, the debug version of inet4 is much too big (500k vs 84k) to go on my floppy disk :oops:

Galvez
Captain Atari
Captain Atari
Posts: 175
Joined: Fri Oct 19, 2007 7:49 am

Re: ROM port Ethernet adapter

Postby Galvez » Mon Apr 09, 2018 9:12 pm

Oops.....I forgot that we were dealing with the ST constrains.
I've strip the binaries, inet4.xdd is around 100k now.

The other problem was a bug in the files used by the Makefile, no rebuilding when a header file was edited to enable debug messages.

rtl8012st_splitvbl_dbg.zip

rtl8012st_busy2dbg.zip
You do not have the required permissions to view the files attached to this post.

User avatar
Xerus
Moderator
Moderator
Posts: 1231
Joined: Fri Dec 13, 2002 9:31 pm
Location: France

Re: ROM port Ethernet adapter

Postby Xerus » Wed Apr 11, 2018 8:55 pm


Galvez
Captain Atari
Captain Atari
Posts: 175
Joined: Fri Oct 19, 2007 7:49 am

Re: ROM port Ethernet adapter

Postby Galvez » Sun Apr 15, 2018 6:28 pm

Thanks a lot for the logs! Sorry for the delay answering.
It looks like I don't install correctly the interrupt for the parallel port, but before I Iook into this further I'd like to solve the problem with the ping.
At first glance I don't see anything, the command doesn't find the route, but it shouldn't be a configuration problem as you told me the same disk works
on the Falcon. I have the feeling that the RTL8012 driver isn't the problem either from the log seems to be working fine.
Do you mind to do a videolog with the disk working on the Falcon?. I'd like to see differences in the log that could give me a hint.
I've attached a RTL8012 debug driver for the Falcon, the rest I think it should work unchanged.

rtl8012falcon030.zip
You do not have the required permissions to view the files attached to this post.

Galvez
Captain Atari
Captain Atari
Posts: 175
Joined: Fri Oct 19, 2007 7:49 am

Re: ROM port Ethernet adapter

Postby Galvez » Tue Apr 17, 2018 7:39 am

Sorry I just noticed that I attached a parallel interrupt version of the driver in my last post, here is the correct one.
rtl8012falcon030.zip

I look into this problem more deeply and I think the driver is OK and the problem is in the kernel or the TCPI/IP stack, I guess almost no one is using MiNT with the ST so the issue has been unnoticed, if this is true it's going to be painful to debug it through video logs. If I have motivation I'll try to reach somebody with a ST around where I live and I'll try to replicate the issue with a NetUSBee card.
You do not have the required permissions to view the files attached to this post.

Galvez
Captain Atari
Captain Atari
Posts: 175
Joined: Fri Oct 19, 2007 7:49 am

Re: ROM port Ethernet adapter

Postby Galvez » Tue Apr 17, 2018 5:23 pm

These drivers attached are for the parallel port interrupt tests. I've done ST and Falcon030 versions, do the tests with the machine you prefer, it's not necessary that you try them in both computers.
rtl8012st_busy1.zip

rtl8012st_busy2.zip

rtl8012st_busy3.zip

rtl8012falcon_busy1.zip

rtl8012falcon_busy2.zip

rtl8012falcon_busy3.zip
You do not have the required permissions to view the files attached to this post.

User avatar
Xerus
Moderator
Moderator
Posts: 1231
Joined: Fri Dec 13, 2002 9:31 pm
Location: France

Re: ROM port Ethernet adapter

Postby Xerus » Tue Apr 17, 2018 9:16 pm

Do not waste your time on the ping.ttp if the driver works, it does not matter.
It will remain a mystery as there are so many ^^

I tested the last 3 drivers (busy) on the STE and sorry none works !

Otherwise I made a videolog of rtl8012falcon030.zip with and without debug:
http://falcon060.free.fr/video/falcon030-debug.3gp
http://falcon060.free.fr/video/falcon030-normal.3gp

Galvez
Captain Atari
Captain Atari
Posts: 175
Joined: Fri Oct 19, 2007 7:49 am

Re: ROM port Ethernet adapter

Postby Galvez » Wed Apr 18, 2018 8:52 am

Thanks again for the logs!

I've taken a look to the disassembled code of the 1.3 version to see how the busy interrupt is installed and I've seen that there is code to install the interrupt handler in the VBI too. Then I've seen that I was fooled to think that the driver was using the busy interrupt because I saw the code there but if I read the code correctly in fact the VBL interrupt is used. If I had direct access to the hardware I'd go further but I think now the driver is good enough. If the 1.3 version author decided to use the VBL instead of the busy interrupt he had good reasons ;-). Just in case I've attached a new driver for the busy interrupt because I saw in the disassembled code (again if I read it correctly) that he installs the interrupt handler first with Setexec() and then with Mfpint(), I thought that one should use one method or the other but let's try this way as a last resort.
rtl8012st_busy4.zip

rtl8012falcon_busy4.zip

Because I'm going to commit the code with the split VBL handler I'd like to test it in the Falcon (we only test it in the ST), it should be ok but to be 100% sure that the code pushed in the repo is working.
rtl8012f030_vbl_final.zip

rtl8012ct60_vbl_final.zip

And finally could you pack the contents of the disk with which you're doing the tests in your ST and send it to me please, so I can try to replicate the pinging issue if I reach around a ST with 4MB of memory.

Thanks a lot for your patience!
You do not have the required permissions to view the files attached to this post.


Social Media

     

Return to “Hardware”

Who is online

Users browsing this forum: No registered users and 4 guests