Re: [PATCH 6/6] Staging: tm6000: Fix coding style issues Fixed coding style issues founded by checkpatch.pl in files: tm6000-alsa.c, tm6000-cards, tm6000-core.c, tm6000-dvb.c, tm6000-i2c.c, tm6000-std
Am 19.06.2010 01:46, schrieb Greg KH: > This patch does not apply properly. What tree did you make it against? > Please redo it against the latest linux-next tree and resend it. > > thanks, > > greg k-h > please look in staging/tm6000 brunch. Stefan Ringel -- Stefan Ringel -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Pending patches for s5p series
Hi, Pending or no comments at these patches. 1. [PATCH/RFC] Samsung multimedia (FIMC and FB) drivers proposal http://marc.info/?l=linux-arm-kernel&m=127668321706310&w=2 2. [PATCH v2] Various s3c-fb updates http://marc.info/?l=linux-arm-kernel&m=127668095702084&w=2 3. [PATCH v2] SDHCI-S3C fixes and enhancements (driver specific code) http://marc.info/?l=linux-arm-kernel&m=127667104617587&w=2 4. [RFC/PATCH 0/9] Samsung crypto engine http://marc.info/?l=linux-arm-kernel&m=127628580015805&w=2 5. [PATCH v2 0/4] ARM: S5P: Support gpio interrupts http://marc.info/?l=linux-arm-kernel&m=127624524906617&w=2 6. [PATCH v4 0/3] Add samsung keypad http://marc.info/?l=linux-arm-kernel&m=127624378103808&w=2 Thank you, Kyungmin Park -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 6/6] Staging: tm6000: Fix coding style issues Fixed coding style issues founded by checkpatch.pl in files: tm6000-alsa.c, tm6000-cards, tm6000-core.c, tm6000-dvb.c, tm6000-i2c.c, tm6000-std
This patch does not apply properly. What tree did you make it against? Please redo it against the latest linux-next tree and resend it. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH] sh_mobile_ceu_camera: fix debugging message
With enabled debugging sh_mobile_ceu_camera.c dereferences an invalid or a NULL pointer. Thanks to James Wang for reporting. Signed-off-by: Guennadi Liakhovetski --- drivers/media/video/sh_mobile_ceu_camera.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/media/video/sh_mobile_ceu_camera.c b/drivers/media/video/sh_mobile_ceu_camera.c index 4ac3b48..3766e30 100644 --- a/drivers/media/video/sh_mobile_ceu_camera.c +++ b/drivers/media/video/sh_mobile_ceu_camera.c @@ -1005,7 +1005,7 @@ static int sh_mobile_ceu_get_formats(struct soc_camera_device *icd, int idx, xlate->code = code; xlate++; dev_dbg(dev, "Providing format %s in pass-through mode\n", - xlate->host_fmt->name); + fmt->name); } return formats; -- 1.6.2.4 -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[cron job] v4l-dvb daily build 2.6.22 and up: ERRORS, 2.6.16-2.6.21: ERRORS
This message is generated daily by a cron job that builds v4l-dvb for the kernels and architectures in the list below. Results of the daily build of v4l-dvb: date:Fri Jun 18 19:00:12 CEST 2010 path:http://www.linuxtv.org/hg/v4l-dvb changeset: 14993:9652f85e688a git master: f6760aa024199cfbce564311dc4bc4d47b6fb349 git media-master: 41c5f984b67b331064e69acc9fca5e99bf73d400 gcc version: i686-linux-gcc (GCC) 4.4.3 host hardware:x86_64 host os: 2.6.32.5 linux-2.6.32.6-armv5: OK linux-2.6.33-armv5: OK linux-2.6.34-armv5: WARNINGS linux-2.6.35-rc1-armv5: ERRORS linux-2.6.32.6-armv5-davinci: OK linux-2.6.33-armv5-davinci: OK linux-2.6.34-armv5-davinci: WARNINGS linux-2.6.35-rc1-armv5-davinci: ERRORS linux-2.6.32.6-armv5-ixp: WARNINGS linux-2.6.33-armv5-ixp: WARNINGS linux-2.6.34-armv5-ixp: WARNINGS linux-2.6.35-rc1-armv5-ixp: ERRORS linux-2.6.32.6-armv5-omap2: OK linux-2.6.33-armv5-omap2: OK linux-2.6.34-armv5-omap2: WARNINGS linux-2.6.35-rc1-armv5-omap2: ERRORS linux-2.6.22.19-i686: ERRORS linux-2.6.23.17-i686: ERRORS linux-2.6.24.7-i686: WARNINGS linux-2.6.25.20-i686: WARNINGS linux-2.6.26.8-i686: WARNINGS linux-2.6.27.44-i686: WARNINGS linux-2.6.28.10-i686: WARNINGS linux-2.6.29.1-i686: WARNINGS linux-2.6.30.10-i686: WARNINGS linux-2.6.31.12-i686: OK linux-2.6.32.6-i686: OK linux-2.6.33-i686: OK linux-2.6.34-i686: WARNINGS linux-2.6.35-rc1-i686: ERRORS linux-2.6.32.6-m32r: OK linux-2.6.33-m32r: OK linux-2.6.34-m32r: WARNINGS linux-2.6.35-rc1-m32r: ERRORS linux-2.6.32.6-mips: OK linux-2.6.33-mips: OK linux-2.6.34-mips: WARNINGS linux-2.6.35-rc1-mips: ERRORS linux-2.6.32.6-powerpc64: OK linux-2.6.33-powerpc64: OK linux-2.6.34-powerpc64: WARNINGS linux-2.6.35-rc1-powerpc64: ERRORS linux-2.6.22.19-x86_64: ERRORS linux-2.6.23.17-x86_64: ERRORS linux-2.6.24.7-x86_64: WARNINGS linux-2.6.25.20-x86_64: WARNINGS linux-2.6.26.8-x86_64: WARNINGS linux-2.6.27.44-x86_64: WARNINGS linux-2.6.28.10-x86_64: WARNINGS linux-2.6.29.1-x86_64: WARNINGS linux-2.6.30.10-x86_64: WARNINGS linux-2.6.31.12-x86_64: OK linux-2.6.32.6-x86_64: OK linux-2.6.33-x86_64: OK linux-2.6.34-x86_64: WARNINGS linux-2.6.35-rc1-x86_64: ERRORS linux-git-armv5: WARNINGS linux-git-armv5-davinci: WARNINGS linux-git-armv5-ixp: WARNINGS linux-git-armv5-omap2: WARNINGS linux-git-i686: WARNINGS linux-git-m32r: OK linux-git-mips: OK linux-git-powerpc64: OK linux-git-x86_64: WARNINGS spec: ERRORS spec-git: OK sparse: ERRORS linux-2.6.16.62-i686: ERRORS linux-2.6.17.14-i686: ERRORS linux-2.6.18.8-i686: ERRORS linux-2.6.19.7-i686: ERRORS linux-2.6.20.21-i686: ERRORS linux-2.6.21.7-i686: ERRORS linux-2.6.16.62-x86_64: ERRORS linux-2.6.17.14-x86_64: ERRORS linux-2.6.18.8-x86_64: ERRORS linux-2.6.19.7-x86_64: ERRORS linux-2.6.20.21-x86_64: ERRORS linux-2.6.21.7-x86_64: ERRORS Detailed results are available here: http://www.xs4all.nl/~hverkuil/logs/Friday.log Full logs are available here: http://www.xs4all.nl/~hverkuil/logs/Friday.tar.bz2 The V4L-DVB specification from this daily build is here: http://www.xs4all.nl/~hverkuil/spec/media.html -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Got internet again, mini-summit report will follow this weekend
Hi all, I got internet in my new apartment this morning, so I hope that I can post the mini-summit report tomorrow or Sunday at the latest. The summit was a smashing success IMHO, although marred for me personally by having to seek medical assistance on Tuesday evening :-( Luckily I did manage to finish the meetings, but I had to skip out on the social events on Tuesday and Wednesday, which was a shame, and I wasn't quite on top form in the afternoons. I can only hope it wasn't too noticable... Luckily we managed to tackle all items on the agenda and finished even a bit ahead of schedule. It was absolutely brilliant to see so many enthusiastic developers willing to contribute to this project and come up with solutions to existing problems. And it is equally clear that we will definitely have more brainstorm meetings and mini-summits in the future since a few days with face-to-face meetings makes it possible to do an amazing amount of work that would take weeks on the mailinglist. Thank you all who contributed to the mini-summit and special thanks to Nokia and Sakari Ailus for hosting and organizing this event! Regards, Hans -- Hans Verkuil - video4linux developer - sponsored by TANDBERG, part of Cisco -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: PROBLEM: 2.6.34-rc7 kernel panics "BUG: unable to handle kernel NULL pointer dereference at (null)" while channel scan runnin
On Sun, Jun 13, 2010 at 11:28 AM, Silamael wrote: > Hello! > > In the meanwhile i tried several different kernel versions: > - 2.6.26 (as included in Debian Lenny): crash > - 2.6.32-3 (as in Debian Squeeze): crash > - 2.6.32-5 (updated version in Debian Squeeze): crash > - 2.6.34: crash > > In every kernel version I've tested, the crashdump looks the same. Each > time there's an NULL pointer given to saa7146_buffer_next(). > > Would be nice if someone could give me some hints. I'm not sure whether > it's a broken driver or it's due to broken hardware or some other issues. > > Thanks a lot! > Matthias, While I don't doubt there's probably a bug in this driver, you haven't provided nearly enough information to correct it. Please resubmit with the full backtrace provided by the kernel at the time of the crash. Without this information, it's hard to gauge the exact cause of the error and thus no one will attempt to fix it. Regards, David Ellingsworth -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Trouble getting DVB-T working with Portuguese transmissions
On Thu, Jun 17, 2010 at 9:00 PM, Richard Zidlicky wrote: > berr is supposed to be the bit error rate. The values displayed here appear > to be > bogus - then again I am not familiar with this particular driver so maybe > just the > error reporting is bogus. The w_scan results also look pretty bad. > > Newest kernel is allways worth a try. I have tried a git snapshot of Linus' 2.6.35 kernel. Is there another non-mainline tree I should try? Would it help to get some kind of dvbsnoop log of this? I've tried doing "dvbsnoop -s pidscan" and "dvbsnoop 0" but didn't get anything that seemed valid. Alternatively what is a well supported usb DVB-T tunner? I've also bought an Avermedia Volar HX and a Gigabyte 7200 which seem to have at best some half-assed out-of-tree drivers. Pedro -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Alternative for defconfig
On Wed, Jun 16, 2010 at 10:56 AM, Tony Lindgren wrote: > * Felipe Contreras [100611 19:03]: >> On Fri, Jun 11, 2010 at 6:07 PM, Laurent Pinchart >> wrote: >> > My understanding is that Linus will remove all ARM defconfigs in 2.6.36, >> > unless someone can convince him not to. >> >> Huh? I thought he was only threatening to remove them[1]. I don't >> think he said he was going to do that without any alternative in >> place. >> >> My suggestion[2] was to have minimal defconfigs so that we could do >> $ cp arch/arm/configs/omap3_beagle_baseconfig .config >> $ echo "" | make ARCH=arm oldconfig >> >> [1] http://article.gmane.org/gmane.linux.kernel/994194 >> [2] http://article.gmane.org/gmane.linux.kernel/995412 > > Sounds like the defconfigs will be going though and we'll use > some Kconfig based system that's still open. I believe Russell > said he is not taking any more defconfig patches, so we should > not merge them either. > > Anyways, we already have multi-omap mostly working for both > mach-omap1 and mach-omap2. Cool, that's a much better approach :) Although it still doesn't solve the problem of default configuration for certain boards... I doubt many people know how to enable USB, audio, and so on. We would probably need some place to share configuration samples and documentation. -- Felipe Contreras -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
