On Nov 14, 2008, at 7:08 PM, Michael Richardson wrote:
No, I actually hadn't allocated it or commited it until I wrote the
email to see if the text made sense.Guy hadn't allocated one, so I
did. I'm actually not certain that I did it right.
You did, although updating the list of LINKTYP
On Nov 13, 2008, at 3:57 PM, David Gibson wrote:
Did this go past on the list (I can't see it on gmane), or has that
gone into a tree somwhere (I can't see it on the default CVS branch)?
It was only in git; I've propagated it to the main and 1.0 CVS branches.
-
This is the tcpdump-workers lis
> "David" == David Gibson <[EMAIL PROTECTED]> writes:
David> Ah, ok, I see. The description looks fine to me, with the
David> exception that the devices are (usually) called
David> /dev/input/event[0-9], not /dev/evd.
Changed this.
--
] ON HUMILITY: to err is human. To
On Fri, Nov 14, 2008 at 10:08:38PM -0500, Michael Richardson wrote:
>
> > "David" == David Gibson <[EMAIL PROTECTED]> writes:
> David> Uh.. so, what's the next step here?
>
> >> I thought Guy already allocated one.
> >>
> >> /* * David Gibson <[EMAIL PROTECTED]> requested thi
> "David" == David Gibson <[EMAIL PROTECTED]> writes:
David> Uh.. so, what's the next step here?
>> I thought Guy already allocated one.
>>
>> /* * David Gibson <[EMAIL PROTECTED]> requested this
>> for # captures from the Linux kernel /dev/evd device. This is
>> used
On Thu, Nov 13, 2008 at 09:22:33AM -0500, Michael Richardson wrote:
>
> > "David" == David Gibson <[EMAIL PROTECTED]> writes:
> >> I was thinking DLT_LINUX_EVDEV just to clarify that it's a
> Linux-internal
> >> protocol, but I'm not fussed by DLT_EVDEV either.
>
> David> Uh.. so
> "David" == David Gibson <[EMAIL PROTECTED]> writes:
>> I was thinking DLT_LINUX_EVDEV just to clarify that it's a Linux-internal
>> protocol, but I'm not fussed by DLT_EVDEV either.
David> Uh.. so, what's the next step here?
I thought Guy already allocated one.
/*
* David
On Mon, Nov 10, 2008 at 08:58:19AM +, David Gibson wrote:
> Michael Richardson sandelman.ottawa.on.ca> writes:
> > > "Guy" == Guy Harris alum.mit.edu> writes:
> > Guy> The name evdev is, as far as I know, a Linuxism, so DLT_EVDEV
> > Guy> might suffice as a name, unless fill-in-th
Michael Richardson sandelman.ottawa.on.ca> writes:
> > "Guy" == Guy Harris alum.mit.edu> writes:
> 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 l
> "Guy" == Guy Harris <[EMAIL PROTECTED]> 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
On Nov 8, 2008, at 7:05 PM, David Gibson wrote:
I have a work-in-progress patch to allow libpcap to capture events
from the Linux input layer's "evdev" interface (/dev/input/event*).
Later I plan to add a wireshark dissector for the packet format.
First, does this seem like a reasonable featur
Hi,
I have a work-in-progress patch to allow libpcap to capture events
from the Linux input layer's "evdev" interface (/dev/input/event*).
Later I plan to add a wireshark dissector for the packet format.
First, does this seem like a reasonable feature to add to libpcap?
Second, if it is, I gathe
12 matches
Mail list logo
