Messages in this thread | | | Subject | Re: [RFC PATCH v2 0/4] Add support for LZ4-compressed kernel | From | Joe Perches <> | Date | Wed, 27 Feb 2013 20:22:54 -0800 |
| |
(removed Richard Purdie and Albin Tonnerre as their email addresses seem to be bounding)
> While recently asking someone to enable VFP debugging, so I could help > sort out a problem they had reported, this is the debug output I was > greeted by thanks to your meddling:
:) Meddling... You sound like one of those nameless villains on Scooby Doo. If only I had a cool nickname like Dave "Shaggy" Kliekamp. I guess you'd have to call me Velma.
> [ 927.235546] \x01\x01\x01\x01\x01\x01\x01\x01 > ... > [ 927.241505] \x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01 > > 7.6 `.asciz "STRING"'... > ======================== > > `.asciz' is just like `.ascii', but each string is followed by a zero > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > byte. The "z" in `.asciz' stands for "zero". > ^^^^^
Yeah, sorry. I thought that the zero was after any concatenation like .c. Learned something. 'preciate that. Would have appreciated a polite "you broke it" email too.
> ??? Yea, right, meanwhile breaking the ability of stuff to produce > kernel messages.
Fortunately, that's the only .S instance.
> > > > > > > so that we can see whether it's worth updating the LZO code > > Sounded as if you were doubtful to me. > _In_ the decompressor. We're talking about the _decompressor_ in > this thread.
My opinion is it's useful to update LZO.
cheers, Joe (aka: Velma)
| |