On Wed, Jun 28, 2017 at 1:18 PM, Eric Anholt wrote:
> I really liked this idea, as it should help with management of packet
> parsing tools like the CL dump. The python script is forked off of theirs
> because our packets are byte-based instead of dwords, and the changes to
> do so while avoiding
Kenneth Graunke writes:
> [ Unknown signature status ]
> On Wednesday, June 28, 2017 11:18:40 AM PDT Eric Anholt wrote:
>> I really liked this idea, as it should help with management of packet
>> parsing tools like the CL dump. The python script is forked off of theirs
>> because our packets are
On Wednesday, June 28, 2017 11:18:40 AM PDT Eric Anholt wrote:
> I really liked this idea, as it should help with management of packet
> parsing tools like the CL dump. The python script is forked off of theirs
> because our packets are byte-based instead of dwords, and the changes to
> do so whil
On Wed, Jun 28, 2017 at 11:18 AM, Eric Anholt wrote:
> I really liked this idea, as it should help with management of packet
> parsing tools like the CL dump. The python script is forked off of theirs
> because our packets are byte-based instead of dwords, and the changes to
> do so while avoidi
Hi Eric,
On 28 June 2017 at 19:18, Eric Anholt wrote:
> I really liked this idea, as it should help with management of packet
> parsing tools like the CL dump. The python script is forked off of theirs
> because our packets are byte-based instead of dwords, and the changes to
> do so while avoid
I really liked this idea, as it should help with management of packet
parsing tools like the CL dump. The python script is forked off of theirs
because our packets are byte-based instead of dwords, and the changes to
do so while avoiding performance regressions due to unaligned accesses
were quite