From: Ben Collins <bcollins@debian.org>
To: Arne Caspari <arnem@informatik.uni-bremen.de>
Cc: Dan Dennedy <dan@dennedy.org>,
Linux1394-Devel <linux1394-devel@lists.sourceforge.net>,
Daniel Drake <dsd@gentoo.org>, Christoph Hellwig <hch@lst.de>,
Adrian Bunk <bunk@stusta.de>,
Damien Douxchamps <ddouxcha@is.naist.jp>,
Parag Warudkar <kernel-stuff@comcast.net>,
Andrew Morton <akpm@osdl.org>, "Randy.Dunlap" <rddunlap@osdl.org>,
Jesper Juhl <juhl-lkml@dif.dk>,
Philippe De Muyter <phdm@macqel.be>,
linux-kernel@vger.kernel.org
Subject: Re: linux1394 patches merged
Date: Sun, 12 Dec 2004 14:34:52 -0500 [thread overview]
Message-ID: <20041212193452.GB18851@phunnypharm.org> (raw)
In-Reply-To: <41B94A27.2010801@informatik.uni-bremen.de>
> Since neither "raw1394" nor "video1394" are drivers specific to the
> devices they define matches for, no other ( specialized ) driver can
> ever get a device object. I am developing a v4l2 driver for the IIDC
> cameras which is based on the "video-2-1394" driver which again is
> designed around the device object and the callbacks of the ieee1394 bus
> driver. This driver never gets loaded since "raw1394" is the first match
> for the device signature and I had to patch "raw1394" and "video1394"
> not to match on anything.
Maybe we need some sort of priority for device matching, or maybe a
"generic" to "specific" probing model.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
prev parent reply other threads:[~2004-12-12 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1102556231.3714.14.camel@kino.dennedy.org>
2004-12-10 7:03 ` Arne Caspari
2004-12-12 19:34 ` Ben Collins [this message]
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=20041212193452.GB18851@phunnypharm.org \
--to=bcollins@debian.org \
--cc=akpm@osdl.org \
--cc=arnem@informatik.uni-bremen.de \
--cc=bunk@stusta.de \
--cc=dan@dennedy.org \
--cc=ddouxcha@is.naist.jp \
--cc=dsd@gentoo.org \
--cc=hch@lst.de \
--cc=juhl-lkml@dif.dk \
--cc=kernel-stuff@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=phdm@macqel.be \
--cc=rddunlap@osdl.org \
/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®