From: Peter Hurley <peter@hurleysoftware.com>
To: Clemens Ladisch <clemens@ladisch.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
devel@driverdev.osuosl.org,
linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging/fwserial: use correct vendor/version IDs
Date: Mon, 02 Feb 2015 17:08:32 -0500 [thread overview]
Message-ID: <54CFF560.300@hurleysoftware.com> (raw)
In-Reply-To: <54C9418F.1050600@ladisch.de>
On 01/28/2015 03:07 PM, Clemens Ladisch wrote:
> The driver was using the vendor ID 0xd00d1e from the FireWire core.
> However, this ID was not registered, and invalid.
>
> Instead, use the vendor/version IDs that now are officially assigned to
> firewire-serial:
> https://ieee1394.wiki.kernel.org/index.php/IEEE_OUI_Assignments
That's great that we have official OUIs now, but I have to NACK this
patch as is.
The problem is a host with the old OUIs will not recognize a remote
unit with the new OUIs, and vice versa.
Even though the new ids could be added to the unit driver's id_table,
(which would let hosts with the new OUI connect to either OUI remote),
it wouldn't let 3.19- hosts connect to 3.20+ hosts.
Regards,
Peter Hurley
next prev parent reply other threads:[~2015-02-02 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54C940E0.5090906@ladisch.de>
2015-01-28 20:07 ` [PATCH] staging/fwserial: use correct vendor/version IDs Clemens Ladisch
2015-01-29 9:44 ` Stefan Richter
2015-02-02 22:08 ` Peter Hurley [this message]
2015-02-03 8:44 ` Stefan Richter
2015-02-03 14:00 ` Peter Hurley
2015-02-03 21:22 ` Stefan Richter
2015-02-07 9:10 ` Greg Kroah-Hartman
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=54CFF560.300@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=clemens@ladisch.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.