From: Richard <ric...@gm...> - 2005-10-11 17:29:44
|
Hi all, I have some problems with the sis900 driver. My network device is listed in 'Syllable Mananger', but it isn't in 'Preferences->Network'. When I look in /var/log/knerl I find these lines: > sis900_probe() found NIC > sis900.c: v1.06.12 03/09/2004 > sis900: Error EERPOM read ffff I hope you could help me out! - Richard |
From: Arno K. <arn...@ya...> - 2005-10-12 08:43:59
|
Richard schrieb: >Hi all, > >I have some problems with the sis900 driver. >My network device is listed in 'Syllable Mananger', but it isn't in >'Preferences->Network'. When I look in /var/log/knerl I find these lines: > > >>sis900_probe() found NIC >>sis900.c: v1.06.12 03/09/2004 >>sis900: Error EERPOM read ffff >> >> >I hope you could help me out! > > If you have a setting like "plug & play os" in your bios then try to disable it. If this doesn´t help then we need the name of the network chip because the sis900 supports different chips. Arno ___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de |
From: Kaj de V. <syl...@fr...> - 2005-10-12 12:09:06
|
> Richard schrieb: >=20 > >Hi all, > > > >I have some problems with the sis900 driver. > >My network device is listed in 'Syllable Mananger', but it isn't in=20 > >'Preferences->Network'. When I look in /var/log/knerl I find these=20 lines: > >=20 > > > >>sis900=5Fprobe() found NIC > >>sis900.c: v1.06.12 03/09/2004 > >>sis900: Error EERPOM read ffff > >>=20 > >> > >I hope you could help me out! > >=20 > > > If you have a setting like "plug & play os" in your bios then try to=20 > disable it. If this doesn=B4t help then we need the name of the network=20 > chip because the sis900 supports different chips. >=20 > Arno Richard already tried that; I pointed him here after he did. :-) Where=20 could he find the chip information in Syllable? Kaj |
From: Arno K. <arn...@ya...> - 2005-10-12 16:25:08
|
Kaj de Vos schrieb: >>If you have a setting like "plug & play os" in your bios then try to >>disable it. If this doesn´t help then we need the name of the network >>chip because the sis900 supports different chips. >> >>Arno >> >> > >Richard already tried that; I pointed him here after he did. :-) Where >could he find the chip information in Syllable? > >Kaj > > > Ok, there seems to be a small difference when reading the mac address between the syllable and the linux driver which _could_ cause this problem. I have changed this and uploaded the updated driver here: http://www.liqwyd.com/arno/sis900.zip Arno ___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de |
From: Steven P. <cod...@bi...> - 2005-10-21 02:55:28
|
I had thought I saw a mailing list topic about this, but apparently not. I've finally got myself a new machine to run Syllable again, but it's using a Marvell Yukon chipset, which isn't supported yet in Syllable. Is there a set of pointers that you could give me about porting drivers over from Linux, and I'll take a shot at it. --Steven |
From: Kristian V. D. V. <va...@li...> - 2005-10-21 12:09:09
|
On Friday 21 October 2005 13:25, Steven Picken wrote: > I've finally got myself a new machine to run Syllable again, but it's > using a Marvell Yukon chipset, which isn't supported yet in Syllable. > Is there a set of pointers that you could give me about porting drivers > over from Linux, and I'll take a shot at it. The only real reference is the current ports, so you'll have to read some of them to get an idea of what needs to be changed. Most of the code will port without changes, although there are some modifications you'll need to make, including but not limited to: o Semaphore & Spinlock types and initialisation o skb management methods are different; there is no skb_put() function, but there is a macro in most lincomp.h headers that emulate it. o Slight differences in the IRQ handlers, and no top-half/bottom-half interupts. o Syllable will require it's own hardware detection routines; PCI access & device management is different in Syllable (Although the actual PCI read/write functions themselves are very similiar) A lot of the differences are hidden via. the header lincomp.h, which provides macros and wrappers for Linux functions that don't exist on Syllable. If you have any questions you can ask here, but the syllable-developer mailing lists may get you more/quicker responses. Good luck! -- Vanders http://www.syllable.org http://www.liqwyd.com |
From: Arno K. <arn...@ya...> - 2005-10-21 12:40:38
|
Steven Picken schrieb: > I had thought I saw a mailing list topic about this, but apparently not. > > I've finally got myself a new machine to run Syllable again, but it's > using a Marvell Yukon chipset, which isn't supported yet in Syllable. > Is there a set of pointers that you could give me about porting > drivers over from Linux, and I'll take a shot at it. > > --Steven I think all syllable network drivers are ports of the linux drivers and so you should first look there. Most of them define the linux net_device structure in their source file. Many also use a file called "linuxcomp.h" which wraps some of the linux commands to syllable. The most complete one seems to be in the file in the dp83815 directory. Some of the functions can´t be wrapped correctly and you have to change the code manually, e.g. the timer and area functions. If you have more questions just post here again. Arno ___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de |