From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-dvb-maintainer@linuxtv.org, video4linux-list@redhat.com,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Rechberger Markus <mrechberger@gmail.com>
Subject: Re: [GIT PATCHES] V4L/DVB updates
Date: Wed, 9 May 2007 21:05:15 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0705092103550.13222@anakin> (raw)
In-Reply-To: <1178706473.9614.31.camel@localhost>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1735 bytes --]
On Wed, 9 May 2007, Mauro Carvalho Chehab wrote:
> Em Qua, 2007-05-09 às 08:30 +0200, Geert Uytterhoeven escreveu:
> > On Fri, 27 Apr 2007, Mauro Carvalho Chehab wrote:
> > > A short changelog:
> > >
> > > - New drivers:
> > > ivtv driver for Hauppauge PVR series and similar boards;
> >
> > Can we please have proper Kconfig dependencies instead of
> >
> > | #ifdef CONFIG_LIRC_I2C
> > | # error "This driver is not compatible with the LIRC I2C kernel configuration
> > | #endif /* CONFIG_LIRC_I2C */
> > |
> > | #ifndef CONFIG_PCI
> > | # error "This driver requires kernel PCI support."
> > | #endif /* CONFIG_PCI */
> >
> > in drivers/media/video/ivtv/ivtv-driver.h? Especially a dependency on
> > CONFIG_PCI would be nice (CONFIG_LIRC_I2C doesn't exist in mainline?).
> >
> > | drivers/media/video/video-buf.c: In function 'videobuf_queue_pci':
> > | drivers/media/video/video-buf.c:399: error: 'pci_map_sg' undeclared (first use in this function)
> >
> > Probably some new driver does a select VIDEO_BUF, which overrides that
> > VIDEO_BUF depends on PCI?
>
> Can you check if the following patch would fix it? VIDEO_BUF is selected
> by several PCI-dependent devices. The only non-PCI device wrongly
> selecting VIDEO_BUF seems to be em28xx.
Yes, it fixed the issues (after manual application of the last chunk,
which didn't apply cleanly). Thanks!
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2007-05-09 19:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 19:59 Mauro Carvalho Chehab
2007-05-09 6:30 ` Geert Uytterhoeven
2007-05-09 10:27 ` Mauro Carvalho Chehab
2007-05-09 19:05 ` Geert Uytterhoeven [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-20 15:18 Mauro Carvalho Chehab
2007-12-24 12:37 Mauro Carvalho Chehab
2007-07-20 19:29 Mauro Carvalho Chehab
2007-07-16 21:34 Mauro Carvalho Chehab
2007-05-22 20:52 Mauro Carvalho Chehab
2007-05-08 18:05 Mauro Carvalho Chehab
2007-05-01 17:40 Mauro Carvalho Chehab
2007-04-15 15:31 Mauro Carvalho Chehab
2007-04-16 15:50 ` Dmitry Torokhov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0705092103550.13222@anakin \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-dvb-maintainer@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mrechberger@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=video4linux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®