On Tue, 2005-27-12 at 10:54 +0100, Stefan Roese wrote: > > Yes, that's the ethernet driver using this access lib to > communicate with the > NPE's. This driver is published under the GPL. >
No experience with the 4xx but some with the other intel NPs. Is the driver a "dual stack" approach that Intel typically has? If the answer is yes, then I would say that without a doubt that crap should never be allowed in. Also any thing that is "multi-os" that you submit for linux will result in you being sent a (dead) fish. So make sure it is not so. Intel should be able to fund you to rewrite it - convincing them they are going to sell more chips this way seems to be not too hard, no? As far as the license for the microcode (If i understood correctly) is concerned if it is BSD that is a big step forward for big bad I. I dont think we have had issues accepting things BSD and as far as i can see this would be a good use of the signed-off part of the patch ;-> i.e You are liable to any lawyer actions from intel given your signed off ;-> (Hrm, would the maintainer of Arm then be liable too? ;-> Always fun playing armchair lawyer) A question for you: Does the 4XX allow you to rewrite the microcode? And if yes, why would you push this intel specific microcode? cheers, jamal - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
