Re: Linux input layer evdev capturing

[Michael Richardson <mcr () sandelman ottawa on ca>]

> > > > > "Guy" == Guy Harris <guy () alum mit edu> writes:

    >> Second, if it is, I gather this is the place to ask for a DLT_
    >> value for this..

    Guy> The name evdev is, as far as I know, a Linuxism, so DLT_EVDEV
    Guy> might suffice as a name, unless fill-in-the-blankBSD or Solaris
    Guy> or... ends up doing their own input layer with a different
    Guy> packet format and calling it evdev, although in that case we
    Guy> could have DLT_FREEBSD_EVDEV or DLT_NETBSD_EVDEV or....

    Guy> Any objections to just DLT_EVDEV?

  It's my understanding that x.org folks expect *BSD or Solaris folks to
either do their own event system, or to do complete rewrite rather than
a port.  (the evdev.c code in xorg includes linux kernel specific
headers)
  So, I suggest DLT_EVDEV, and if we have to, we'll do:
      #define DLT_EVDEV_LINUX DLT_EVDEV
  when we get a request for a similar, but incompatible event system.

-- 
]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr () sandelman ottawa on ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.