How is it going with that? Is there anyone working on drivers for X5000 any more? I am not so well versed in programming but you would think that if just one person would be working on the driver it would be finished if he had been at it for over a year.

Last edited by Niolator on 28-Feb-2018 at 10:46 PM.

@Niolator

It depends what else that one developer is working on and how much time they can dedicate to the NIC. Having said that, they will have get the driver out some time since Tabor's release depends on it.

@Niolator

Given the time frame the onboard LAN driver for X1000 took to get finished, (iirc it's in beta and still not released upto today) you may want to stock up your popcorn for some years to come.

@Niolator

just wait couple of week more.

_________________
I love Amiga and new hope by AmigaNG
A 500 + ; CDTV; CD32;
PowerMac G5 Quad 8GB,SSD,SSHD,7800gtx,Radeon R5 230 2GB;
MacBook Pro Retina I7 2.3ghz;
#nomorea-eoninmyhome

@Niolator

How you dare to ask about ?! Maybe you also want DMA in graphics.library for x5000 ?! :) But, seriusly, no one is working on it, imho.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@kas1e

Quote:

But, seriusly, no one is working on it, imho.

Let me correct you.

A-EON Technology Ltd contracted Costel Mincea of Hyperion Entertainment CVBA to create the SANA network driver for X5000 and A1222 and additionally complete the X1000 driver project. The contract was signed at the Amiga 30th event in Peterborough, UK in August 2015. Payment was made for the contract in full within the following month and as I understand work has been ongoing steadfastly since on all three projects with breaks in the development for the various X5000/A1222 ISO preparation work and Kernel debugging/testing. With respect to Cyrus and Tabor, a few complications on converting the large complex/bloated Linux driver code to a suitable Amiga SANA driver format were cited as the initial roadblocks if I recall correctly.

_________________
Amiga Kit Amiga Store
Links: www.amigakit.com | New Products | A600GS

@amigakit

Good to have an update. It's not been a massive issue on my X1000 as the network card works perfectly and has done since day one.

_________________
Sam

@-Sam-

Regarding the Linux drivers:
As quoted by Xeno74 http://forum.hyperion-entertainment.biz/viewtopic.php?f=58&t=3892&start=80

We added the QorIQ DPAA Ethernet driver to the X5000 Linux kernel and Darren's new Cyrus eth dtb to the Linux kernel package. Unfortunately the QorIQ DPAA Ethernet driver has some problems. Jamie and Skateman have tested a lot the DPAA Ethernet and have found some issues. They figured out that we have to configure the MAC addresses in U-Boot because there aren't any MAC addresses configured. It seems the serial eeprom on the Cyrus board wasn't programmed with MAC addresses. This is where U-Boot gets its MAC addresses from if you haven't programmed the U-Boot variables. Darren told us that Linux looks in the device tree to see which ethernet ports to attach. On the earlier kernels (based on the SDK) we had no problems, as the aliases used to link dTSEC's to eth ports was in the board description file, however at some point Freescale moved the p5020 board aliases to the p5020si-pre.dtsi file, which messes up our system as we include that too meaning conflicts. It seems we need to get the device tree fixed, that's where the problem is. I figured out that the DPAA Ethernet driver has only been available since the mainline vanilla kernel 4.10. This driver isn't available for older kernels like 4.9, 4.8, etc.
Jamie and Skateman have posted the issue on the linuxppc-dev mailing list. Madalin Bucur created a mdio patch to avoid MDIO bus removal when a PHY is missing. This patch was added to the RC9. We had a little success with disabling the PAMU support in the X5000 kernel. Without the PAMU support, Skateman was able to configure a manual IP address and he was also able to ping his gateway, and even DNS queries work without any problems. Unfortunately if he generates to much packets, then all traffic dies because it isn't enough buffer space available. He was able to increase the buffer space with 'ip link set eth0 qlen 10000'. Jamie's X5000 was able to obtain an IP address via DHCP. He captured with Wireshark which showed a successful DHCP request/response for the X5000/20, followed by some failed ping attempts. Even when the interface does obtain an IP address via DHCP (about half the time), subsequent traffic still fails to receive responses. I hope we can solve the issue with the DPAA Ethernet driver.

There is plenty work in progress

_________________
AmigaOne X5000 -> 2GHz / 16GB RAM / Radeon R7 250 / M-Audio 5.1 -> AmigaOS 4.1 FE / Ubuntu Linux
Amiga 1200 -> Recapped / 68ec020 ACA 1221ec / CF HDD / RetroNET connected to the world

@amigakit

Yes, thanks for the infornation.

@Skateman

The suggestion was made to Hyperion to develop the Amiga driver derived from the simpler and smaller Uboot network driver due to the reduced code base from the Linux version.

_________________
Amiga Kit Amiga Store
Links: www.amigakit.com | New Products | A600GS

My X1000 has been running with an off the shelf network card since day 1 with no issues and I'm assuming the X5000 isn't relying soley on an onboard network device so unless the onboard device is magically much faster than the card that's been working great from day 1 why bother

_________________
____________________________
c64-2sids, A1000, A1200T-060@50(finally working!),A4000-CSMKIII
! My Master Miggies- Amiga 1000 & AmigaOne X1000 !
mancave-ramblings
X1000 I BELIEVE

@klx300r

Well it would be nice to use the on-board one - frees up a slot!

_________________
Sam

@Raziel

Quote:

Raziel wrote: @Niolator Given the time frame the onboard LAN driver for X1000 took to get finished, (iirc it's in beta and still not released upto today) you may want to stock up your popcorn for some years to come.

I thought about that myself, but the PA6T-1682M is no longer supported, while the P5020 still is, so Amiga developers must still have access to resources from the vendor.

_________________
---------------
AmigaOne X5000 P5020 2Ghz, OS 4.1
AmigaOne XE G4 800mhz, OS 4.1
A1200T 40Mhz 68040, OS 3.9

@-Sam-

Quote:

-Sam- wrote: @klx300r Well it would be nice to use the on-board one - frees up a slot!

Exactly. My 2 PCI slots are taken up with a SATA card and the network card. I'm using a very budget PCI-e sound card. I would love to ditch the network card and get a better PCI sound card.

Also, I believe there is a compatibility issue with some sound cards and using more than 4 GB under Linux. (not that I use Linux much).

_________________
---------------
AmigaOne X5000 P5020 2Ghz, OS 4.1
AmigaOne XE G4 800mhz, OS 4.1
A1200T 40Mhz 68040, OS 3.9

@klx300r

The X5000 NIC, part of the P5020 SOC is another cup of tea (and a big pain to get these up and running correctly)

P5020: QorIQ® P5020 and P5010 64-bit Dual- and Single-Core Communications Processors

Ethernet interfaces
10 Gbps Ethernet MAC
Five 1 Gbps Ethernet MACs

The P5 platform leverages architectural features pioneered in the P4 platform, including the three-level cache hierarchy for low latencies, hardware hypervisor for robust virtualization support, data path acceleration architecture (DPAA) for offloading packet handling tasks from the core and the CoreNet® switch fabric that eliminates internal bottlenecks. This enables architectural compatibility from the P5 platform to the P4 platform as well as to the P3 platform.

And yes.. i do have a pci-e X1 Realtek NIC in the X5000, but i would love to get the onboard NIC up and running.

_________________
AmigaOne X5000 -> 2GHz / 16GB RAM / Radeon R7 250 / M-Audio 5.1 -> AmigaOS 4.1 FE / Ubuntu Linux
Amiga 1200 -> Recapped / 68ec020 ACA 1221ec / CF HDD / RetroNET connected to the world

@amigakit

Quote:

The suggestion was made to Hyperion to develop the Amiga driver derived from the simpler and smaller Uboot network driver due to the reduced code base from the Linux version.

While porting the existing Ethernet driver for the X5000 from the U-Boot
sources would work to provide a working Ethernet on the motherboard, and
free up an expansion slot in the process, it is not without it's downside.

The U-Boot sources make use of the p5020's "Independent Ethernet Mode",
which is designed for early boot code, like U-Boot, where you want networking
before you have the rest of the hardware fully available.

This not only means that it ignores the hardware accelerated offloading
of much of the network data stream, made available via the Data Path
Acceleration Architecture (DPAA), it is also limited to 100-Mbps rates.

So the end result would be on-board Ethernet that was potentially
10 times slower than the 1 Gbps Ethernet board in an expansion
slot.

Therefore, in my mind the only option worth going for in the long run
is to use the DPAA. Without it you gain very little, while simultaneously
giving up a lot in the process.

However, like Skateman pointed out, the DPAA is a whole new "cup of tea".

The DPAA is complex to setup properly, due mainly to the wide range
of functionality it was designed to handle, and the fact that the
Cyrus (X5000) board differs from the Freescale/NXP reference boards
for which the Linux driver was developed.

This is why the current DPAA Ethernet drivers under Linux are broken
on the X5000 at the moment.

_________________
Jamie Krueger
BITbyBIT Software Group LLC
jamie@bitbybitsoftwaregroup.com
PLEASE NOTE: I only speak for myself and my company,
and am not a spokesperson for Amiga Inc.

@daveyw

Quote:

Quote: Quote: Raziel wrote: @Niolator Given the time frame the onboard LAN driver for X1000 took to get finished, (iirc it's in beta and still not released upto today) you may want to stock up your popcorn for some years to come. I thought about that myself, but the PA6T-1682M is no longer supported, while the P5020 still is, so Amiga developers must still have access to resources from the vendor.

That is true for *now*, but it *was* supported (when the X1000 came out) for a long time where they could have added support "easily" (with the backing of those hardware vendors).
So, at least for me, that's no excuse.

Actually, watching all of this with a step taken back, that whole picture looks even more fragmented.

If i'd still be interested in anything coming from AmigaKit, i'd be very pissed by all those "soon to be released" announcements that still took months if not years to be delivered.

Just like it was with the years before...they do deliver eventually, ok, but they are always too late.

Perfect example:
The X1000 onboard LAN driver.
The hardware itself is already EOL, it's not produced, not sold and not cared for anymore, and there is still no driver for an essential part of the mainboard.

Does anyone really think that the X5000 onboard LAN driver will take another road?
Don't hold your breath

@Raziel

Why not hold my breath?

I took several reads in the Freescale/NXP docs. The P5020 SoC can be a real pain in the a**, especially regarding the I/O setup and DMA setup. Even the P1022 isn´t really easy to handle. Setup alone is like Sysiphos´s work for both, and you could make a _lot_ of mistakes with this.

I fully understand that such a work takes time, as it may lead to some heavy frustration on developer´s side for sure.

@whose
Soon 3 years then for network drivers. Its just too much, does not matter how developers may be frustrated.

I can understand when developers come with all the alphas betas every weeks or something, saying about problems, asking for help of how to fix them, then all can be done fast.

But.. as it now, i give you my words : no network drivers in the next 2 years.

Maybe Tabor in a year or two, without sound drivers of course :)

I do not know what all those problems, and why it all take so long.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@kas1e

I dont think the Focus has been on the network drivers at all. Like mentioned before both machines X1000 and X5000 came with a working network soluton.

If A-EON chose to solder a cheapass Realtek chip onboard the problem would not even exist.

Like someone once mentioned to me, A-EON chose for some fancy..but complex hardware instead of the cheap mainstream components. Was this a wise choice... who knows

Last edited by Skateman on 03-Mar-2018 at 09:10 AM.

_________________
AmigaOne X5000 -> 2GHz / 16GB RAM / Radeon R7 250 / M-Audio 5.1 -> AmigaOS 4.1 FE / Ubuntu Linux
Amiga 1200 -> Recapped / 68ec020 ACA 1221ec / CF HDD / RetroNET connected to the world