Jack,
On Fri, Sep 15, 2006 at 07:01:25PM -0700, Jack Vogel wrote:
J> >J> In the last attempt to merge community CVS with Intel internal code I
J> >J> came across an issue I'd like to bring up.
J> >J>
J> >J> There is an ancient e1000 card, pci id 1000, an 82542, that we
J> >J> don't have in our s
On 9/15/06, Gleb Smirnoff <[EMAIL PROTECTED]> wrote:
On Mon, Sep 11, 2006 at 02:02:58PM -0700, Jack Vogel wrote:
J> In the last attempt to merge community CVS with Intel internal code I
J> came across an issue I'd like to bring up.
J>
J> There is an ancient e1000 card, pci id 1000, an 82542, that
On Mon, Sep 11, 2006 at 02:02:58PM -0700, Jack Vogel wrote:
J> In the last attempt to merge community CVS with Intel internal code I
J> came across an issue I'd like to bring up.
J>
J> There is an ancient e1000 card, pci id 1000, an 82542, that we
J> don't have in our source, yet community cvs sti
Jack Vogel wrote this message on Mon, Sep 11, 2006 at 14:02 -0700:
> I just had our test group hunt up one of these and test, and sure
> enough, the driver recognizes it, but it does NOT pass traffic.
>
> Clearly no one is using these, at least not with STABLE :) and
> as Intel does not want to su
In the last attempt to merge community CVS with Intel internal code I
came across an issue I'd like to bring up.
There is an ancient e1000 card, pci id 1000, an 82542, that we
don't have in our source, yet community cvs still does. Support
for this was removed from Linux long ago because the card
