| To: | ravinandan.arakali@xxxxxxxxxxxx |
|---|---|
| Subject: | Re: default directive in Kconfig(subject modified) |
| From: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
| Date: | Mon, 08 Aug 2005 19:38:16 -0700 (PDT) |
| Cc: | hch@xxxxxxxxxxxxx, raghavendra.koushik@xxxxxxxxxxxx, jgarzik@xxxxxxxxx, netdev@xxxxxxxxxxx, leonid.grossman@xxxxxxxxxxxx, rapuru.sriram@xxxxxxxxxxxx |
| In-reply-to: | <002801c59c7a$fb660ec0$4810100a@xxxxxxxxxxx> |
| References: | <002801c59c7a$fb660ec0$4810100a@xxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
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> |
|---|---|---|
| ||
| Previous by Date: | default directive in Kconfig(subject modified), Ravinandan Arakali |
|---|---|
| Next by Date: | RE: default directive in Kconfig(subject modified), Ravinandan Arakali |
| Previous by Thread: | default directive in Kconfig(subject modified), Ravinandan Arakali |
| Next by Thread: | RE: default directive in Kconfig(subject modified), Ravinandan Arakali |
| Indexes: | [Date] [Thread] [Top] [All Lists] |