Re: linux camera drivers
Mayank, On Sat, Mar 3, 2012 at 9:51 AM, Mayank Agarwal mayank77fromin...@gmail.comwrote: On Fri, Mar 2, 2012 at 10:08 AM, Mayank Agarwal mayank77fromin...@gmail.com wrote: 1.I think the device supports i2c or spi protocol.I want to know how the i2c or spi is taking data from image sensor and giving it to video buffers. Most of the cameras support i2c or csi. 2.I want to understand the whole data flow from image sensor to the display buffer and the role of linux kernel camera drivers in that. For this you need to understand the V4L2 Framework, Or later Media Controller Framework. 3.Currently i am looking at Sony IMX036,Aptima MT9P031. You can find in directory source/drivers/media/video/ MT9p031 support is there in current kernel but no idea about imx036. Regards, ---Prabhakar Lad Mob: +91-9611756433 http://in.linkedin.com/pub/prabhakar-lad/19/92b/955 Thanks and Regards, Mayank On Thu, Mar 1, 2012 at 8:22 PM, Greg KH g...@kroah.com wrote: On Thu, Mar 01, 2012 at 05:57:52PM +0530, Mayank Agarwal wrote: Hi all, I have following questions regarding camera drivers in linux kernel. 1.which are the files/folder in kernel directory where camera drivers support is provided in linux kernel. It depends, which type of protocol does your device support? 2.Are they customisable according to different SOC requirements. It depends on what the requirements are. As it's software, it's always able to be changed :) 3.Are there any tutorials/pdfs to understand camera drivers in linux kernel. What is wrong with the code itself? 4.At present which sensor (i mean aptina/sony/omnivision) drivers are supported in linux kernel. What sensor are you looking for exactly? What device do you need to support, and what protocol does your camera use to talk to the hardware? greg k-h ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
slacks usage,..
Hi All, I am going through below topic http://patches.linaro.org/6833/. I could not got the meaning of slacks. Why I need this .. Is there some real example of need of slacks. Thanks ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: slacks usage,..
On Mon, Mar 5, 2012 at 11:00 AM, trisha yad trisha1ma...@gmail.com wrote: Hi All, I am going through below topic http://patches.linaro.org/6833/. I could not got the meaning of slacks. Why I need this .. Is there some real example of need of slacks. Have you tried searching for it? :D [1]. thanks, Daniel. [1] https://lwn.net/Articles/369549/ ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: slacks usage,..
Thanks Daniel, I got it ^^. On Mon, Mar 5, 2012 at 2:52 PM, Daniel Baluta daniel.bal...@gmail.com wrote: On Mon, Mar 5, 2012 at 11:00 AM, trisha yad trisha1ma...@gmail.com wrote: Hi All, I am going through below topic http://patches.linaro.org/6833/. I could not got the meaning of slacks. Why I need this .. Is there some real example of need of slacks. Have you tried searching for it? :D [1]. thanks, Daniel. [1] https://lwn.net/Articles/369549/ ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: slacks usage,..
Thanks a lot. On Mon, Mar 5, 2012 at 4:11 PM, naveen yadav yad.nav...@gmail.com wrote: Thanks Daniel, I got it ^^. On Mon, Mar 5, 2012 at 2:52 PM, Daniel Baluta daniel.bal...@gmail.com wrote: On Mon, Mar 5, 2012 at 11:00 AM, trisha yad trisha1ma...@gmail.com wrote: Hi All, I am going through below topic http://patches.linaro.org/6833/. I could not got the meaning of slacks. Why I need this .. Is there some real example of need of slacks. Have you tried searching for it? :D [1]. thanks, Daniel. [1] https://lwn.net/Articles/369549/ ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: kernel boot procedure
@Vladimir Murzin--thnx. for the link..really interesting it is.. @Santosh sir, Quoting from: http://www.ibm.com/developerworks/linux/library/l-initrd/index.html *The initial RAM disk (initrd) is an initial root file system that is mounted prior to when the real root file system is available. The initrd is bound to the kernel and loaded as part of the kernel boot procedure. The kernel then mounts this initrd as part of the two-stage boot process to load the modules to make the real file systems available and get at the real root file system.* We were just at BIOS-MBR-bootloader at MBR(GRUB/LILO)- 1.does GRUB/LILO understand/see the filesystems --so that it mounts the initrd image or the kernel image bcz. they both are in /boot(harddisk filesystems) 2.does the kernel mounts initrd as root filesystem??? or the bootloader does this task?? ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: kernel boot procedure
Hi On Mon, Mar 5, 2012 at 3:58 PM, beyond.hack beyond.h...@gmail.com wrote: @Vladimir Murzin--thnx. for the link..really interesting it is.. @Santosh sir, Quoting from: http://www.ibm.com/developerworks/linux/library/l-initrd/index.html The initial RAM disk (initrd) is an initial root file system that is mounted prior to when the real root file system is available. The initrd is bound to the kernel and loaded as part of the kernel boot procedure. The kernel then mounts this initrd as part of the two-stage boot process to load the modules to make the real file systems available and get at the real root file system. We were just at BIOS-MBR-bootloader at MBR(GRUB/LILO)- 1.does GRUB/LILO understand/see the filesystems --so that it mounts the initrd image or the kernel image bcz. they both are in /boot(harddisk filesystems) 2.does the kernel mounts initrd as root filesystem??? or the bootloader does this task?? ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies 1. Yes, they understand filesystems. They provide their own (may be simplified) support for access to filesystem. 2. Yes, kernel mounts rootfs from initrd as a root mount point, later it overwrote with actual root file system ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Need help: Generating patch using git
You can remote track linux-next from your existing repo. (this is how I do it.) cd into your linux-2.6/ and do this; $ git remote add linux-next git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git $ git fetch linux-next $ git fetch --tags linux-next You will then be all set up to track linux-next. Then, in the future, do 'git remote update' to update the linux-next branch so you get all the latest tags each time (this will also update any other remote branches you have set up to track). Note that as I understand it linux-next isn't an 'evolving' tree like mainline, it's best to see it as being a list of individual kernels released as tags, i.e. you shouldn't be merging one into another. Stephen Rothwell's notification on the linux-kernel mailing list about the latest release explains this and is probably worth a read: https://lkml.org/lkml/2012/2/1/20 To list the tags, do: $ git tag -l next-* and the bottom one will be the latest linux-next version. So in my repo, having just done a remote update, the last few tags look like this: $ git tag -l next-* ... next-20111215 next-20111216 next-20111221 next-20111228 next-20120113 next-20120118 next-20120201 The bottom one is the latest release so I can check out this tag, like so, (with accompanying message below:) $ git checkout next-20120201 Checking out files: 100% (2741/2741), done. Note: checking out 'next-20120201'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b new_branch_name HEAD is now at bc7f599... Add linux-next specific files for 20120201 Then I can create a new branch from here, e.g. $ git checkout -b 1st-feb-2012-next Now I have my own branch to build a linux-next kernel, or work on, etc. I have followed the steps as mentioned above and I have created a new branch which has some trivial changes. After this I ran checkpatch.pl script against my patch, which reported no warning or error messages. I sent this patch to myself and was able to apply this patch successfully(In past It didn't worked as I was using gmail GUI client which does not work for sending patches, refer Documentation/email-clients.txt). As this patch does nothing more than just adding some missing loglevels for printks', hence I was wondering if I need to go through the entire kernel build process and boot from the modified kernel and do some tests before sending this patch to kernel-janitor mailing list and the relevant maintainers. To be specific, my changes are under linux-next/net/ipv4 I've read SubmittingPatches but still I wish to know the general steps that one should follow for janitorial related changes. -Amit P.S. What i think is trivial can very much be substantial as well as I may not perceive the effects as of now. ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Linux cdc-acm-driver
On Mon, Mar 05, 2012 at 03:24:17PM +0400, tamerlan311 wrote: This kernel module was completely stable. But i think that i should do some clean up code before upstream it. There's no need to do that now, you can always send follow-on patches doing that. Was planned for future developments: implement write to device support. (I do not know why, but this feature was implemented in original source) How can a barcode scanner be written to? implement work in UNI-Directional mode (0c2e:0710) I am busy working, but I'll try to finish in few week. How about I take what you have now, that ensures we make the 3.4 kernel release deadline, and then you send follow-on patches for the other things as you work on them? That way people can use the driver now, which is what they want to do :) thanks, greg k-h ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
