Re: adding if_dev member to struct ifnet

From: Daniel C. Sobral (dcs_at_tcoip.com.br)
Date: 10/07/03

  • Next message: Bruce Evans: "Re: sys/conf/DEFAULT[S]"
    Date: Tue, 07 Oct 2003 13:44:13 -0300
    To: Brooks Davis <brooks@one-eyed-alien.net>
    
    

    Brooks Davis wrote:

    >
    > Not today, since none of them get used in the paths that do this. In
    > general the network code doesn't care what you call an interface. There
    > are a few corners where it does, but nothing that isn't specific to
    > a certain set of drivers. Additionally, it is necessary to not have
    > members called if_name and if_unit if we have if_xname as the primary
    > driver name. It's also worth noting that one of the things I want to do
    > is break the driver+unit mapping for certain types of pseudo devices.
    > Specifically vlan devices should be allocatable by creating an interface
    > with a name like fxp0.100 so while you could synthesize a unit number,
    > it wouldn't have any useful meaning.

    I wonder how that works for vlans over bridges...

    -- 
    Daniel C. Sobral
    Gerência de Operações
    Divisão de Comunicação de Dados
    Coordenação de Segurança
    VIVO Centro Oeste Norte
    Fones: 55-61-313-7654/Cel: 55-61-9618-0904
    E-mail:	Daniel.Capo@tco.net.br
    	Daniel.Sobral@tcoip.com.br
    	dcs@tcoip.com.br
    _______________________________________________
    freebsd-arch@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-arch
    To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
    

  • Next message: Bruce Evans: "Re: sys/conf/DEFAULT[S]"

    Relevant Pages

    • Re: adding if_dev member to struct ifnet
      ... > general the network code doesn't care what you call an interface. ... > a certain set of drivers. ... > is break the driver+unit mapping for certain types of pseudo devices. ... > Specifically vlan devices should be allocatable by creating an interface ...
      (freebsd-net)
    • Re: HARDWARE: Open-Source-Friendly Graphics Cards -- Viable?
      ... I expect we'll come out with PCI and AGP ... Standardizing the hardware interface lowers the cost of doing an OS ... been writing and maintaining drivers for years... ...
      (Linux-Kernel)
    • VESA fb weirdness in 2.6.0-test4-mm4
      ... Vesafb is announcing itself as: ... quite slow, but compared to *cough* some other fb drivers, it is at least ... # ACPI (Advanced Configuration and Power Interface) Support ...
      (Linux-Kernel)
    • [RFC] Proposal: common kernel-wide GPIO interface
      ... More and more devices these days come with some sort of GPIO interface, and more and more drivers within the kernel could make use of a common way of accessing pins on such an interface, not to mention userspace apps. ... For example, we have the I2C, LED, and SPI subsystems that each could drive a device that's actually connected to some GPIO pins somewhere. ...
      (Linux-Kernel)
    • Being more anal about iospace accesses..
      ... (MMIO), mainly because on a PC ... pointer directly, and it will actually work on most machines. ... result some drivers didn't use a pointer at all, ... Sometimes such a "mixed interface" driver does it based on a compile ...
      (Linux-Kernel)