[WORKING]SiS900 Ethernet Driver

Posted 06 April 2008 - 01:05 AM

The driver is based on linux driver , and R1000 driver of this forum (Thank's DaemonES)

The driver is working !! (I'm connected with ! on Tiger)

but you can help because I have only one SiS900 at home and it's one with the RLT8201 PHY transmitter.

you can test the driver by downloading the zip and start by clicking on "myload.command".Next you have to put the dmesg log in a file and post it on the board.

Thank's

[EDIT] 8 April:_Correction of an Rx bug ( Now the driver is stable )_Detection of the cable9 April:_Big optimisation on Tx and Rx (Before:900KB/s of 1800KB/s with 100%CPU. After: 1800KB/s of 1800KB/s with 25%CPU)

Posted 09 August 2008 - 01:21 AM

Guest: BuildSmart_*

Posted 09 August 2008 - 03:01 PM

The driver is based on linux driver , and R1000 driver of this forum (Thank's DaemonES)

The driver is working !! (I'm connected with ! on Tiger)

but you can help because I have only one SiS900 at home and it's one with the RLT8201 PHY transmitter.

you can test the driver by downloading the zip and start by clicking on "myload.command".Next you have to put the dmesg log in a file and post it on the board.

Thank's

[EDIT] 8 April:_Correction of an Rx bug ( Now the driver is stable )_Detection of the cable9 April:_Big optimisation on Tx and Rx (Before:900KB/s of 1800KB/s with 100%CPU. After: 1800KB/s of 1800KB/s with 25%CPU)

Where to begin??? (netwarrior)

Nice attempt, well thought out, could have been planned a little better and separated into 2 separate classes but a very solid base to work from.

I took the liberty of redoing the project and cleaning it up a little.

You match on the raw device however it appears that there are two different subsystem ID's corresponding to two seperate device chipset and it might have been better to use this information to identify the driver class to use rather than using all of that code to detect which chipset is included and then use the appropriate code but splitting it into two classes isn't a requirement.

I changed the way the project builds and populates the Info.plist so anyone looking at the project wont be so confused by the tree, changed the class name to SiS900, added some comments and added comments to the original linux files which are listed in the project and thus available from within XCode so they can be used as references material.

Removed SiS900_reg.h (duplication wasn't necessary in this case) and using the linux header file was the method selected.

I see you tried to build this as a universal binary however the exclusive use of i386/pio.h prevents a useable compilation for ppc and I don't believe you will find a ppc machine with these cards so I made the project i386 only for all configuration.

I'd like to help you improve this project and hope you are not offended in what I've done with your project.

Here is the archive, go over it and see if it looks any better to you, if so add it to your first post and it can be the base project for all future changes.

Guest: BuildSmart_*

Posted 09 August 2008 - 07:15 PM

Guest: BuildSmart_*

Guests

this is my error after running command please help

kextunload: /Users/thesmart1/Desktop/SiS900/build/Debug/SiS900-loadable.kext: no such bundle file existscan't add kext (file access/permissions).chown: build/Debug/SiS900.kext: No such file or directorychmod: build/Debug/SiS900.kext: No such file or directorymv: rename build/Debug/SiS900.kext to build/Debug/SiS900-loadable.kext: No such file or directorycp: build/Debug/iwi3945-loadable.kext/Contents/MacOS/SiS900: No such file or directorykextload: /Users/thesmart1/Desktop/SiS900/build/Debug/SiS900-loadable.kext: no such bundle file existscan't add kernel extension build/Debug/SiS900-loadable.kext (file access/permissions) (run kextload on this kext with -t for diagnostic output)logout[Process completed]thaank you

You are executing command files without knowing what they are doing, utterly amazing!!!

I suggest you refrain from using XCode before you cause serious damage to your Mac OS X installation until you have a better understanding of what you are doing.

How did you make that driver from linux driver??

I would like to try with other chips that have no driver for mac but have for linux...

I would say it was done using common sense and an understanding of programming, there is no easy way to do it and only a general guideline to follow.

Posted 09 August 2008 - 07:46 PM

Guest: BuildSmart_*

Posted 10 August 2008 - 03:53 AM

Guest: BuildSmart_*

Guests

can you explain how i can please i really need your help

Find the linux driver for the card you have and port the source over to Mac OS X, if you don't understand what this means then you don't have enough experience as a programmer to achieve your intended results.

I recommend you wait until someone has made a driver for your card or replace your card with one that works OOB.

These please of desperate help don't appeal to many programmers so if it's something you have to have now then you need hire someone qualified to generate a driver for you if you can't wait or don't want to change your card for one that works.

Posted 10 August 2008 - 11:20 PM

Nice attempt, well thought out, could have been planned a little better and separated into 2 separate classes but a very solid base to work from.

I took the liberty of redoing the project and cleaning it up a little.

You match on the raw device however it appears that there are two different subsystem ID's corresponding to two seperate device chipset and it might have been better to use this information to identify the driver class to use rather than using all of that code to detect which chipset is included and then use the appropriate code but splitting it into two classes isn't a requirement.

I changed the way the project builds and populates the Info.plist so anyone looking at the project wont be so confused by the tree, changed the class name to SiS900, added some comments and added comments to the original linux files which are listed in the project and thus available from within XCode so they can be used as references material.

Removed SiS900_reg.h (duplication wasn't necessary in this case) and using the linux header file was the method selected.

I see you tried to build this as a universal binary however the exclusive use of i386/pio.h prevents a useable compilation for ppc and I don't believe you will find a ppc machine with these cards so I made the project i386 only for all configuration.

I'd like to help you improve this project and hope you are not offended in what I've done with your project.

Here is the archive, go over it and see if it looks any better to you, if so add it to your first post and it can be the base project for all future changes.

Hello ,

Ho nice to see someone using this driver , ... I wrote this driver in 3 days :/so it wasn't really clean , now I can't help because I broken my computer , you can create a new Topic with your file because I am not here really often and i can't change the main post each times you update the driver .

I hope you to make this driver working with all Physical transmiters (I'm sur that will be done in few hours of coding )

Guest: BuildSmart_*

Posted 11 August 2008 - 02:41 AM

Guest: BuildSmart_*

Guests

Hello ,

Ho nice to see someone using this driver , ... I wrote this driver in 3 days :/so it wasn't really clean , now I can't help because I broken my computer , you can create a new Topic with your file because I am not here really often and i can't change the main post each times you update the driver .

I hope you to make this driver working with all Physical transmiters (I'm sur that will be done in few hours of coding )

Good luck Bye!

I don't have the time to work on it exclusively and I can't take over some one else's project, I was willing to help with correcting issues and reorganizing the code to address the PHY issues but if you're not developing it any more then I'll give it up cause I don't have the hardware to test the code on and relying on users here for intelligent feedback or some kind or programming knowledge when developing a driver has proven to be a poor option.

Posted 12 August 2008 - 02:02 AM

Guest: BuildSmart_*

Posted 12 August 2008 - 02:37 AM

Guest: BuildSmart_*

Guests

buildsmart dont be a {censored} if you dont wanna help me fine with me but keep ur fuc8 mouth shut and keep going on with your life............

Dude you tried to contact me for private help and I told you no private help is available and that you should post publicly, you continued to contact me privately begging for help and I decided I would not provide you with any help and now you leave a foul mouthed post because I refused to help you but failed to realize I provided you with the information to solve the problem and this was posted before I told you I would not provide you with any more assistance.

Please grow up, your childish antics wont help you get your problem solved and I told you I would not help you further.

Are you upset because I have the knowledge and ability to resolve the problem but refuse to assist you further because you can't read my signature or the fact that you're incapable of resolving the problem yourself and no one wants to help you?

Save yourself and refrain from posting a reply, you don't want to look any worse than you already do.