On Monday 07 March 2011 22:00:25 hlabishi kobo wrote:
> Linus suggested to me that i should print the window and see how it
> looks, I did that and it returns this ef0fffffe, ffbffff, f70fffff,
> eb1b53c0, eb3950b8, eb1749c0. I am not sure if this are hexadecimal
> number or what.

I would think that you wrote the part which prints out this values. This means 
that you know which parameters you gave printk and that you should know the 
conversation specifiers and length modifiers that you used in the format 
string.

But I would guess without having any of these information that you used %x to 
print these values. Whatever you used as argument - 32 bit (size of single 
int) of it were printed in unsigned in hexidecimal notation. Maybe you should 
think about using %lx to print unsigned long ints in hexidecimal notation in 
case you really used %x.

Which brings me to another question: Why to I see 6 numbers in your post and 
why has the first one 9 nibbles?

As said before (and also recommended by Linus): try to write a small c program 
which uses these values, print the single bits, try to write some test 
algorithm using these decoded bits and play a little bit around with other 
test inputs before trying random things inside the kernel.

> Again this is the results of printing seq_bits, so far
> i have not been able to print real_bits as this cannot even make a
> network ping. Could you enlighten me in this case.

I cannot understand how pings and printks are related...


May I ask how these things are related to your work/studies? It is ok to play 
around a little bit as small side project/hobby without having the time and 
knowledge to understand what you are really doing. That is usually a good way 
to find new interesting topics and maybe to learn something (or blow up a 
building...). But I would highly recommend to switch the topic in case this is 
part of your thesis or work.

It is not meant as harsh criticism of what you try to do, but it seems that 
right now you aren't able to efficiently work with it and to gain enough 
knowledge by yourself to be able to understand simple parts the thing you are 
working with.

Best regards,
        Sven

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to