netdev
[Top] [All Lists]

RE: default directive in Kconfig(subject modified)

To: "'David S. Miller'" <davem@xxxxxxxxxxxxx>
Subject: RE: default directive in Kconfig(subject modified)
From: "Ravinandan Arakali" <ravinandan.arakali@xxxxxxxxxxxx>
Date: Tue, 9 Aug 2005 14:26:05 -0700
Cc: <hch@xxxxxxxxxxxxx>, <raghavendra.koushik@xxxxxxxxxxxx>, <jgarzik@xxxxxxxxx>, <netdev@xxxxxxxxxxx>, <leonid.grossman@xxxxxxxxxxxx>, <rapuru.sriram@xxxxxxxxxxxx>
Importance: Normal
In-reply-to: <20050808.193816.70216612.davem@xxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
Yes, I got the run-time feature message. It will require quite
a bit of code reshuffle and testing to make sure we don't
break existing code in any way.

Thanks,
Ravi

-----Original Message-----
From: David S. Miller [mailto:davem@xxxxxxxxxxxxx]
Sent: Monday, August 08, 2005 7:38 PM
To: ravinandan.arakali@xxxxxxxxxxxx
Cc: hch@xxxxxxxxxxxxx; raghavendra.koushik@xxxxxxxxxxxx;
jgarzik@xxxxxxxxx; netdev@xxxxxxxxxxx; leonid.grossman@xxxxxxxxxxxx;
rapuru.sriram@xxxxxxxxxxxx
Subject: Re: default directive in Kconfig(subject modified)


From: "Ravinandan Arakali" <ravinandan.arakali@xxxxxxxxxxxx>
Date: Mon, 8 Aug 2005 17:40:45 -0700

> Can somebody throw light on the below subject ?
> We have S2io configured as a module and 2buff mode is
> one of the suboptions under S2io. But a directive such
> as "default y" does not seem to enable 2buff mode.

Independant of this issue, can you please acknowledge what
many people are trying to show you in that you MUST make
this a run-time selectable feature.

Yes, that means the driver will have to have two totally
seperate code paths.  But that should not be inefficient
because you can just hook up different transmit and
interrupt handler methods depending upon the mode selected.


<Prev in Thread] Current Thread [Next in Thread>