|
Who's Online
|
16 user(s) are online (9 user(s) are browsing Forums)
Members: 0
Guests: 16
more... |
|
|
|
Hans [image]
|
Re: wireless networking |
|
Quite a regular
From:
New Zealand
|
|
Posts:
874
|
|
Posted on: 9/1 23:01:19
|
|
@ncafferkey
Quote:
ncafferkey wrote:
Adding WPA2 should be reasonably straightforward, as it can be done in hardware.
Good to hear.
Quote:
What would it need to be "proper"? The included WirelessManager is a port of wpa_supplicant, and this component handles scanning, association, setting up of encryption, and other management functions. It has the advantage that it should in theory work with all existing TCP/IP stacks. Enabling enterprise features is probably just a matter of linking with necessary libraries such as SSL.
Oh, I thought that WirelessManager was a tool specific to that device driver. My apologies if this is not the case. Specifically what I meant was a stack that manages all wifi devices (logins, encryption, etc.), and provides the TCP/IP stack with whatever additional info wireless connections usually provide.
One thing that I think is important is to be able to have per-wireless access point firewall settings as opposed to one setting per wifi card. Yes, I know, our firewall has no GUI, but I see this as important. I can't see how you could achieve this with a SANA-II driver, or without some modifications to the TCP/IP stack.
While you're here, are you going to make an Amiga OS 4.x version?
Hans
|
|
|
 Transfer
|
|
|
|
|
Hans [image]
|
Re: wireless networking |
|
Quite a regular
From:
New Zealand
|
|
Posts:
874
|
|
Posted on: 8/31 18:15:03
|
|
@kolla
Quote:
kolla wrote:
@Hans
I was only talking about the wireless stack, not the IP stack.
And I was also talking about the wireless stack too. My point was that the IP stack is based on BSD code, and so a BSD wireless stack might be a good fit. One major difficulty is that Roadshow is based on BSD4.4 (IIRC), which is from the mid-nineties. There's a good chance that this makes working on a wireless stack a waste of time until Roadshow is updated, which was discussed in the gigabit ethernet thread. I think that an updated IP stack should be a higher priority, anyway.
Quote:If you feel you have spare time you want to kill, then feel free to have a go at the various 802.11 frameworks in the various BSDs and/or Linux kernel, and port wpa_supplicant or open1x, or the opensea supplicant... come back in 5 years and show us what you have running :)
Why do I have such confidense? I've been working with wireless professionally since 2002 and have seen how long it has taken on all the widely used platforms to get things going, and none of them are by any means done yet.
Once again, my suggestion is to leverage the work already done on another platform instead of starting from scratch. Yes, it would still be a lot of work, but it would be a lot less than writing one from scratch.
Added to this, I find people saying "it's too much work," and "it's too hard," rather annoying. I've been working on my RadeonHD driver in my spare time for two years now, and I'm still working on it. However, thanks to me just getting to work, we're now in a position where we can soon take advantage of a new motherboard with a 16x PCI-Express port. If I had been a wimp and said "this is too much work," then the A1-X1000 would be looking less enticing with a (approx. ten year old) PCI Radeon card as graphics card.
So, I encourage developers to think creatively, sub-divide the problem into manageable chunks, and work on them one by one. Take a slightly longer term view of things. If we only work on stuff that can be achieved quickly, then we're never going to move forward. Engineering is no place for wimps.
Hans
|
|
|
| Transfer
|
|
|
|
|
Hans [image]
|
Re: Gigabit ethernet? |
|
Quite a regular
From:
New Zealand
|
|
Posts:
874
|
|
Posted on: 8/26 21:44:18
|
|
@Cyborg
Quote:
Cyborg wrote:
To make good use of 1Gbit we'd need a new TCP stack based on modern BSD network kernel as well as an updated SANA2 specification (or even a completely new SANA3), which are aware of such high rates and accordingly written (i.e. avoiding memcpy() whereever possible, making use of DMA capabilities of network chips, support for jumbo frames, etc. pp.).
Out of curiosity, which version of BSD would be the best to use as the starting point for an updated TCP stack? AFAIK, BSD4.4 was the end of the line for BSD itself, and it forked into FreeBSD, OpenBSD, and a bunch of others.
I'm not familiar with the BSD variants at all, so I don't know which would provide the best basis.
Hans
|
|
|
| Transfer
|
|
|
|
|
Hans [image]
|
Re: Radeon 5000 Open Source 2D-3D |
|
Quite a regular
From:
New Zealand
|
|
Posts:
874
|
|
Posted on: 8/21 7:01:27
|
|
@Arcane5150
Quote:
Arcane5150 wrote:
Would this be a step forward in getting hardware acceration? From what I can tell if it is supporting OpenGL, then MiniGL should be able to be supported somewhat. Anyways, I'll leave the decisions to the people in the know, but the 5000 series has some nice cards.
In short, having a chunk of Linux code doesn't really help. It doesn't make good documentation, and it can't just be recompiled for Amiga OS. The Linux graphics system is very different from Amiga's, and so it's still necessary to write Amiga OS 4.x specific drivers.
Supporting Evergreen cards is not a priority at the moment. I have 2D acceleration done for R500 series chipsets, and am working on 2D acceleration for R600/R700 chipsets (i.e., Radeon HD 2000/3000/4000 cards). Getting 3D support for these cards is more important than trying to keep up with the very latest generation.
Currently there are no Radeon HD 5000 series cards that I could plug into my A1, even if I did want to chase the latest and greatest. Added to that, the Evergreen MESA drivers, are DRI style drivers (i.e., using the old, deprecated API) not Gallium ones, and so that's not very helpful. Gallium 3D drivers are available for the cards currently supported by my RadeonHD driver, and that will make getting 3D working a lot easier.
I will get to the Radeon HD 5000 series eventually, but it's important that support for the R500-R700 series is finished off first.
Hans
P.S. I briefly had the latest Radeon HD card series supported when I got the Radeon 4350 framebuffer working. AMD released the Radeon HD 5000 series a few weeks later.
|
|
|
| Transfer
|
|
|
|
Home |
|
All Posts (Hans)
