View Single Post
Old 02 January 2019, 17:12   #12
RichardP
Registered User

 
Join Date: Dec 2018
Location: Cambridge
Posts: 13
Quote:
Originally Posted by Niklas View Post
Thank you Olaf for your comments. I noticed in the SANA-II specification revision 4 that you are quite the expert in this area :-)

I think there were two main reasons why I was considering the bsdsocket.library option initially:

1. I'm not exactly a Linux expert, and setting up the necessary routing on the Raspberry Pi to route datagrams to and from the Amiga felt like it would take a bit of learning for me. With the bsdsocket.library approach I would write a normal user-mode Linux application that communicated with the Amiga and then made the corresponding socket API calls.

2. I read somewhere that running the TCP/IP stack on an A500 takes quite a bit of memory (not sure if this is actually true), and therefore I thought I'd do as much off-loading to the Raspberry Pi as possible.

However, after reading your comments I'm motivated to investigate the SANA-II route more carefully. Learning how to set up the routing on the Raspberry Pi (I suppose I may have to create a pseudo Ethernet device, or a PPP link) should be interesting in and of itself.

2. I have not managed to get the IP stack to run properly on a 1MB Amiga 500.. it barely runs on a 1.5MB A600

On the Linux box, you can create a basic Ethernet device - that has just memory IO's .. and then add it to a linux Bridge.
https://www.xml.com/ldd/chapter/book/ch14.html

Linux Device Drivers book is the gospel

Some sample skeleton..
https://kernel.googlesource.com/pub/...net/skeleton.c

In the end, there will be three interfaces on the Raspberry... eth0, fakeAmiga0 and Bridge0. Bridge0 will have eth0 and fakeAmiga0 devices enslaved and will behave like a network switch. ( bridge-utils linux package)
RichardP is offline  
 
Page generated in 0.04271 seconds with 11 queries