From: Michael Hunold <hunold@convergence.de>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org, video4linux-list@redhat.com
Subject: Re: [2.6 patch] select for drivers/media
Date: Sun, 28 Sep 2003 23:04:12 +0200 [thread overview]
Message-ID: <3F774CCC.3040707@convergence.de> (raw)
In-Reply-To: <20030928160536.GJ15338@fs.tum.de>
Hello Adrian,
> The patch below switches drivers/mtd to use select where appropriate.
Ok.
> Could someone with a knowledge of the code please check the following:
>
> DVB_AV7110 and DVB_BUDGET select VIDEO_SAA7146 (without my patch
> VIDEO_SAA7146 depends on them) although they don't fulfill the
> VIDEO_SAA7146 dependencies VIDEO_DEV && PCI && I2C.
I admit that this is somewhat broken and might fail under certain
cirumstances. It's possible that someone sets DVB_AV7110, but does not
have I2C enabled. Then VIDEO_SAA7146 is not build, although it should. Doh!
Does your patch fix this issue as well?
> Is the intention to enable VIDEO_SAA7146 only when these options are
> enabled or should DVB_AV7110 and DVB_BUDGET depend on these options?
Both DVB_AV7110 and DVB_BUDGET need VIDEO_SAA7146 to work properly. Same
goes for the analog video drivers VIDEO_MXB, VIDEO_DPC and the other
saa7146 drivers.
It's somewhat annoying that you have to enable I2C before all these
drivers can be build. The user needs to know that I2C is used somewhere
in the driver, although he won't see anything -- all i2c drivers are
compiled automatically, a "modprobe mxb" loads all i2c drivers it needs.
It would be better, if I2C would be enabled automatically if SAA7146 is
set. I admit that this sort of reversed-selection can introduce new
problems.
What do you think?
> cu
> Adrian
CU
Michael.
next prev parent reply other threads:[~2003-09-28 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 16:05 [2.6 patch] select for drivers/media Adrian Bunk
2003-09-28 21:04 ` Michael Hunold [this message]
2003-09-28 21:26 ` Adrian Bunk
2003-09-29 17:30 ` Greg KH
2003-09-29 18:31 ` Michael Hunold
2003-09-29 19:10 ` Roman Zippel
2003-10-01 16:39 ` Michael Hunold
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=3F774CCC.3040707@convergence.de \
--to=hunold@convergence.de \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.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