Re: [Q] tracing/printing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


Not sure, but this may help you:



2012/3/14 Ezequiel García <elezegarcia@xxxxxxxxx>:
> Hi,
> I'm writing a video capture device and have a doubt about how to
> correctly print to screen.
> First, I suppose I should follow the rule "don't print unless there is
> something surprising to say", right?
> Second, I've found I need to print in a very verbose manner
> at developing stage so I should implement a debug param.
> I will probably adopt videobuf2 way (like many others) of
> defining a macro (dprintk or something).
> However, reading the source I've found there isn't a unified
> way to do this: some use printk (as defined macros), others
> use v4l_xxx, others use dev_xxx.
> I've adopted the latter, because I thought there could
> be many devices plugged, and using dev_xxx with
> the usb_device->dev helps seeing which is tracing.
> I'm not really sure if it is ok so I would love to
> hear some opinions about this sensible issue.
> Thanks!
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at

Peter Senna Tschudin
gpg id: 48274C36

Kernelnewbies mailing list

[Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Photo]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Networking]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]

  Powered by Linux