I noticed this in the Begroovy forums. MYOB posted a topic regarding the new 3Com driver by Patrick Lafarguette. This might interest some BeOS PowerPC users if you haven’t already read his post:
Yet another historic BeOS limitation seems to have been shattered - the 10Mbit barrier for PowerPC network cards.
Patrick Lafarguette, who wrote the Intersil Prism drivers and the 3Com 940 Gigabit ethernet drivers for x86 BeOS has ported his 3Com 920 driver to PPC, and has added support for the 905B chipset to it, one of the most common 100Mbit network cards in existance.
I tried with my 905C-TX card, and its recognised but crashes the network stack on any IP but 192.168.0.1, which is my router and hence not usable… However, this could be an issue with the C revision chipset
So, any other PPC users with 3Com cards, give it a go: http://bebits.com/app/3551
So, if you run BeOS on a PowerPC and have one of the mentioned NICs that this driver supports, then try it out on your PowerPC.
[powered by WordPress.]
Random Haiku:
Application crash!
Polite message shuts it down...
The rest keep working.
Since 1998 - Until the Last User Leaves...
— BeGroovy, established 1998
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
| « Sep | ||||||
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | ||||||
22 queries. 0.050 seconds
[powered by WordPress.]
November 8th, 2004 at 11:22 am
Patrick sent me a debug version of the driver to try to see whats breaking on my machine, which I’ll be running after I’ve had dinner
It’ll be nice to be able to use a REAL network card and not a Farallon EtherMac on PPC - those are so hard to find now.
November 8th, 2004 at 11:31 am
This is great and all, but I’d rather have a utility for measuring the signal strength / ect, on the prism driver.
November 8th, 2004 at 12:06 pm
I’m working on that. He said that once I can provide an API that he can use to bind the driver info to a monitor app, he’ll add it to the driver
At the moment, the support isn’t actually in the driver, so it can’t be done. And he, like most BeOS users, I hope; sees the value of having one standard API for network discovery, etc, so other wireless card drivers can use the same zeroconf tools, the same network stumblers, etc.
November 8th, 2004 at 4:46 pm
Does the BeBox have the same issue?