Re: Source organization for two drivers sharing coomon code

Thanks for all the answers. The common code is mostly handling the message passing for hardware initialization, rings creation and some ioctls. drivers/message looks like a good place for this code to live. Subbu From: Jan Engelhardt [mailto:[EMAIL PROTECTED] To: Chris Friesen [mailto

Source organization for two drivers sharing coomon code

like to avoid duplicating the common code under the two driver directories. Is there any recommened way to organize such common code ? Thanks. Subbu ___ This message, together with any attachment(s), contains

Regarding KDB for REDHAT9.0

Hi I have REDHAT 9.0 (kernel version 2.4.20-8) and i want to have KDB. please tell me which version of KDB i can use with redhat 9.0 and above mentioned kernel version. TIA Subbu "SASKEN RATED THE BEST EMPLOYER IN THE COUNTRY by the BUSINESS TODAY Mercer Survey

Network Driver Name (ATM Driver)

be included in the code to get the same..?? Kindly reply back to this mail ID and [EMAIL PROTECTED] Thanks in Advance Subbu "SASKEN RATED THE BEST EMPLOYER IN THE COUNTRY by the BUSINESS TODAY Mercer Survey 2004" SASKEN BUSINESS DISCLAIMER This message

how to detect the n/w driver name at user level.

. Thanx in advance Subbu ___ ___ A.V.Subba Rao SEMICON-DSL group SASKEN COMMUNICATION TECHNOLOGIES LTD. 139/25,AMARJYOTI LAYOUT, RING ROAD, DOMULUR