|To:||Ben Greear <greearb@xxxxxxxxxxxxxxx>|
|Subject:||Re: SIOCADDMULTI for unicast broken|
|From:||Jeff Garzik <jgarzik@xxxxxxxxx>|
|Date:||Fri, 03 Jan 2003 20:52:13 -0500|
|Cc:||Donald Becker <becker@xxxxxxxxx>, jamal <hadi@xxxxxxxxxx>, netdev@xxxxxxxxxxx|
|User-agent:||Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202|
Ben Greear wrote:
Donald Becker wrote:
> Maybe in a proc file system that the driver
No! procfs additions are discouraged. sysfs in 2.5.x if you _must_ do this, but SIOCDEVPRIVATE or just flat out maintaining a kernel patch against a stable kernel tree would be much preferred, I think.
> It would be neat to see various driver-specific features
like this be implemented, and it would be even nicer if they followed at least some general guideline for how to interface with the rest of the world...
Driver-specific features are by definition just that :) If you want a general guideline, you'll also want a header or helper lib quite often to eliminate duplication of code and standardize the interface.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: SIOCADDMULTI for unicast broken, Donald Becker|
|Next by Date:||Re: SIOCADDMULTI for unicast broken, jamal|
|Previous by Thread:||Re: SIOCADDMULTI for unicast broken, jamal|
|Next by Thread:||Re: SIOCADDMULTI for unicast broken, Krzysztof Halasa|
|Indexes:||[Date] [Thread] [Top] [All Lists]|