search for: linville

Hello, I am creating a configuration where a Redhat server running bridge-tools 0.9.5 will be bridging between different VLANs on the same physical interface (for example: a bridge consisting of eth1.100 and eth1.110). This physical interface is being connected to modern Cisco switches running PVST+. The Cisco switch does not like this configuration as the tags on its BPDUs are being changed

Is anyone using sk98lin Gigabit Ethernet adapters under CentOS 4.x? The version of the driver that ships with CentOS 4.x kernels was too old to support the onboard NICs on some Intel server boards that we recently got, so we installed a newer driver using DKMS. However, we're having problems finding a stable driver to use: the first version that we tried (7.09) gave a kernel panic when I ran

<I apologize if this arrives twice... I sent it first from an non-subscribed address, don't know if that'll get to the list or not --JJ> Hi folks, I have an implementation question regarding bridging on a linux box between a catalyst trunk port and a cisco 26something w/802.1q subinterfaces. So right now, there's no vlan trunking going on on the link my bridging firewall sits

We should prefer `const struct pci_device_id` over `DEFINE_PCI_DEVICE_TABLE` to meet kernel coding style guidelines. This issue was reported by checkpatch. A simplified version of the semantic patch that makes this change is as follows (http://coccinelle.lip6.fr/): // <smpl> @@ identifier i; declarer name DEFINE_PCI_DEVICE_TABLE; initializer z; @@ - DEFINE_PCI_DEVICE_TABLE(i) + const

We should prefer `const struct pci_device_id` over `DEFINE_PCI_DEVICE_TABLE` to meet kernel coding style guidelines. This issue was reported by checkpatch. A simplified version of the semantic patch that makes this change is as follows (http://coccinelle.lip6.fr/): // <smpl> @@ identifier i; declarer name DEFINE_PCI_DEVICE_TABLE; initializer z; @@ - DEFINE_PCI_DEVICE_TABLE(i) + const

...uld prefer `const struct pci_device_id` over > `DEFINE_PCI_DEVICE_TABLE` to meet kernel coding style guidelines. > This issue was reported by checkpatch. Honestly, I prefer the macro -- it stands-out more. Maybe the style guidelines and/or checkpatch should change instead? John -- John W. Linville Someday the world will need a hero, and you linville at tuxdriver.com might be all we have. Be ready.

On Fri, Jul 18, 2014 at 12:22:13PM -0400, John W. Linville wrote: > On Fri, Jul 18, 2014 at 05:26:47PM +0200, Benoit Taine wrote: > > We should prefer `const struct pci_device_id` over > > `DEFINE_PCI_DEVICE_TABLE` to meet kernel coding style guidelines. > > This issue was reported by checkpatch. > > Honestly, I prefer the macro...

On Fri, Jul 18, 2014 at 12:22:13PM -0400, John W. Linville wrote: > On Fri, Jul 18, 2014 at 05:26:47PM +0200, Benoit Taine wrote: > > We should prefer `const struct pci_device_id` over > > `DEFINE_PCI_DEVICE_TABLE` to meet kernel coding style guidelines. > > This issue was reported by checkpatch. > > Honestly, I prefer the macro...

Not sure yet what or where the problems are but having just done a jum update on my HP laptop (nw8240) and my IBM desktop from 2.6.9.42.0.2.EL the laptop is locking up during boot sequence and the desktop when running VMware Workstation seems to take all CPU and makes strange noises from the loudspeaker. Using grub to fall back to last kernel all is ok again !!. Ian -------------- next part

Any hope of getting my laptop's Broadcom BCM94311 wireless running on CentOS 5? I find lots of references to using fwcutter to get the needed firmware from Windows drivers, but there's a Catch-22: Version of fwcutter that generate files for the bcm43xx driver in CentOS 5 don't recognize the md5sum of any currently available Windows driver. Newer versions of fwcutter

I'm new to the lists so sorry about any faux pas I may have made. Also I apologize for the length, but I wanted to be sure I covered most of the details. I'm trying to do a PXE install on an Intel 1435VP2 server machine. The PXE install has worked on all the older machines in the cluster, so I know PXE is working. However, these new Intel server machines only support PXE booting from

Hi, What is the easiest way to bridge between two user-space processes that talk directly to Ethernet interfaces? I have two applications that write/read Ethernet frames to/from Linux Ethernet ports (e.g. eth0). The applications can successfully talk to each other when they run on two machines connected over Ethernet. I would like to be able to test them on a single machine without employing

Hi, We have a simple bridge setup but the ping (and other network traffic) does not work reliably. After tracing the code, it looks like a software bug. Since bridge software is been running by thousands of people. I guess I am wrong. Anyway, here is the problem. There are 2 boxes and each one has 2 interfaces, 1 ethernet and 1 wifi. STP is enabled for the bridge to avoid the loop. So the box 1

...vem@davemloft.net> David S. Miller <davem@davemloft.net> Eric Paris <eparis@redhat.com> Fabio Porcedda <fabio.porcedda@gmail.com> Greg Kroah-Hartman <gregkh@linuxfoundation.org> Ingo Molnar <mingo@kernel.org> Jiri Kosina <jkosina@suse.cz> John W. Linville <linville@tuxdriver.com> Kees Cook <keescook@chromium.org> Kirill A. Shutemov <kirill@shutemov.name> Li Zefan <lizefan@huawei.com> Lino Sanfilippo <LinoSanfilipp@gmx.de> Linus Torvalds <torvalds@linux-foundation.org> Oliver Neukum <oliver@neukum.or...

Could someone provide the steps to create a driver disk for CentOS 4? I found some documentation describing steps to create one for CentOS 3 but I think it's slightly different since CentOS 4 uses the 2.6 kernel. Any help is appreciated.

David, if it's not too late, please pull the following last minute fix into 2.6.34. Thanks! The following changes since commit de02d72bb3cc5b3d4c873db4ca8291723dd48479: Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6 (2010-05-10 22:53:41 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git net-2.6 Michael S. Tsirkin (1): vhost: fix barrier pairing drivers/vhost/vhost.c | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-)...

David, if it's not too late, please pull the following last minute fix into 2.6.34. Thanks! The following changes since commit de02d72bb3cc5b3d4c873db4ca8291723dd48479: Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6 (2010-05-10 22:53:41 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git net-2.6 Michael S. Tsirkin (1): vhost: fix barrier pairing drivers/vhost/vhost.c | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-)...

On Fri, Jul 18, 2014 at 09:54:32AM -0700, James Bottomley wrote: > On Fri, 2014-07-18 at 09:43 -0700, Greg KH wrote: > > On Fri, Jul 18, 2014 at 12:22:13PM -0400, John W. Linville wrote: > > > On Fri, Jul 18, 2014 at 05:26:47PM +0200, Benoit Taine wrote: > > > > We should prefer `const struct pci_device_id` over > > > > `DEFINE_PCI_DEVICE_TABLE` to meet kernel coding style guidelines. > > > > This issue was reported by checkpatch....

.... Also correct a bug in util.c. The comparison with ETH_P_802_3_MIN should be >= not >. As suggested by Jesse Gross. Compile tested only. Cc: David Miller <davem at davemloft.net> Cc: Jesse Gross <jesse at nicira.com> Cc: Karsten Keil <isdn at linux-pingi.de> Cc: John W. Linville <linville at tuxdriver.com> Cc: Johannes Berg <johannes at sipsolutions.net> Cc: Bart De Schuymer <bart.de.schuymer at pandora.be> Cc: Stephen Hemminger <stephen at networkplumber.org> Cc: Patrick McHardy <kaber at trash.net> Cc: Marcel Holtmann <marcel at holtmann....

...y at hansenpartnership.com> wrote: > On Fri, 2014-07-18 at 11:17 -0700, Greg KH wrote: >> On Fri, Jul 18, 2014 at 09:54:32AM -0700, James Bottomley wrote: >> > On Fri, 2014-07-18 at 09:43 -0700, Greg KH wrote: >> > > On Fri, Jul 18, 2014 at 12:22:13PM -0400, John W. Linville wrote: >> > > > On Fri, Jul 18, 2014 at 05:26:47PM +0200, Benoit Taine wrote: >> > > > > We should prefer `const struct pci_device_id` over >> > > > > `DEFINE_PCI_DEVICE_TABLE` to meet kernel coding style guidelines. >> > > > > Th...