Hi Alex,

Thanks. By variants, I mean maybe different kernels may have different
in-kernel drivers.
So if there are a lot of kernel versions, there may be a lot of driver
versions, which I call them variants.
In this case, the Click Router project has to develop a lot of patches for
those variants.

However, if the in-kernel drivers are basically the same among different
kernel versions, the Click Router Project may be able to issue patches for
them.

best
Bingyang

On Mon, Nov 14, 2011 at 4:59 PM, Alexander Duyck <
[email protected]> wrote:

> Hi Bingyang,
>
> I'm not sure what you mean by variants.  The driver I am referring to is
> the one included with a given kernel.  Odds are the Click Router project
> is already having to include patches for the kernel itself in order to
> enable support for its features.  If that is the case they might be able
> to also include a patch for the e1000 driver within the kernel so that
> it can be used instead of having to load an additional network driver
> from SourceForge in order to support their project.
>
> Thanks,
>
> Alex
>
> On 11/14/2011 12:05 PM, Bingyang LIU wrote:
> > Hi Alex,
> >
> > Are there many variants of in-kernel drivers? If there are many, I
> > don't think the Click Router Project can follow all the variants.
> >
> > thanks.
> > Bingyang
> >
> > On Mon, Nov 14, 2011 at 2:57 PM, Alexander Duyck
> > <[email protected] <mailto:[email protected]>>
> wrote:
> >
> >     Hi Bingyang,
> >
> >     You might want to work with the maintainers for the Click Router
> >     project
> >     in order to see if they can provide you with updated patches for the
> >     in-kernel version of the driver.
> >
> >     If we were to update e1000 you would still need updated patches in
> >     order
> >     for things to work due to a number of changes we would need to make
> in
> >     order for the driver to support changes in the kernel.  If they can
> >     provide you with updated patch that works with the in-kernel
> >     drivers it
> >     would likely help to resolve this issue and any issues that should
> >     come
> >     up with that driver going forward.
> >
> >     Thanks,
> >
> >     Alex
> >
> >     On 11/14/2011 10:47 AM, Bingyang LIU wrote:
> >     > Hi Alex,
> >     >
> >     > Thank you very much for your reply.
> >     >
> >     > Actually, the in-kernel driver works just fine.
> >     > However, I want to use kernel mode Click Router
> >     > <http://read.cs.ucla.edu/click/> with polling function. Click
> router
> >     > provides patches for some e1000 drivers (2.x, 4.x, 5.x, 6.x, 7.x,
> >     > 7.3.20, 7.6.15.5 and e-0.4.1.7) to achieve my goal, but the
> >     problem is
> >     > that these e1000 drivers cannot work with kernel 2.6.32-31.
> >     >
> >     > best
> >     > Bingyang
> >     >
> >     > On Fri, Nov 11, 2011 at 12:00 PM, Alexander Duyck
> >     > <[email protected]
> >     <mailto:[email protected]>
> >     <mailto:[email protected]
> >     <mailto:[email protected]>>> wrote:
> >     >
> >     >     On 11/10/2011 09:11 PM, Bingyang LIU wrote:
> >     >     > Hi all,
> >     >     >
> >     >     > I was trying to install e1000-7.6.15.5 on unbuntu 10.04,
> whose
> >     >     kernel
> >     >     > version is 2.6.32.-31.
> >     >     >
> >     >     > However, e1000 driver uses a linux kernel structure
> >     >     "net_device", which
> >     >     > seems obsolete, and a new struct net_device_ops is used in
> >     2.6.31+.
> >     >     >
> >     >     > So, does any one know how to use the e1000 driver on
> >      2.6.31+ ?
> >     >     >
> >     >     > thanks very much!
> >     >     >
> >     >     > best
> >     >     > Bingyang
> >     >     Bingyang,
> >     >
> >     >     There should be an e1000 driver included with the 2.6.31
> >     kernel that
> >     >     will support your product.
> >     >
> >     >     Is there a specific feature your require that is currently
> >     not present
> >     >     in the 2.6.32 kernel?  I ask because we are planning to
> >     change to a
> >     >     kernel only maintenance model for e1000 on/around Q2 of
> >     2012.  If you
> >     >     have an open issue that is resolved in the sourceforge
> >     driver that is
> >     >     not addressed in the in-kernel driver please submit a bug on
> >     >     http://sourceforge.net/projects/e1000/support so that we
> >     might address
> >     >     it prior to discontinuing maintenance for the sourceforge
> >     driver.
> >     >
> >     >     Thanks,
> >     >
> >     >     Alex
> >     >
> >     >
> >     >
> >     >
> >     > --
> >     > Bingyang Liu
> >     > Network Architecture Lab, Network Center,Tsinghua Univ.
> >     > Beijing, China
> >     > Home Page: http://netarchlab.tsinghua.edu.cn/~liuby
> >     <http://netarchlab.tsinghua.edu.cn/%7Eliuby>
> >     > <http://netarchlab.tsinghua.edu.cn/%7Eliuby>
> >
> >
> >
> >
> > --
> > Bingyang Liu
> > Network Architecture Lab, Network Center,Tsinghua Univ.
> > Beijing, China
> > Home Page: http://netarchlab.tsinghua.edu.cn/~liuby
> > <http://netarchlab.tsinghua.edu.cn/%7Eliuby>
>
>


-- 
Bingyang Liu
Network Architecture Lab, Network Center,Tsinghua Univ.
Beijing, China
Home Page: http://netarchlab.tsinghua.edu.cn/~liuby
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to