On Wed, Jan 28, 2015 at 09:07:43PM +0100, 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:
>
On Wed, Jan 28, 2015 at 09:07:43PM +0100, 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:
On Feb 03 Peter Hurley wrote:
> On 02/03/2015 03:44 AM, Stefan Richter wrote:
> > On Feb 02 Peter Hurley wrote:
[...]
> >> 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
On 02/03/2015 03:44 AM, Stefan Richter wrote:
> On Feb 02 Peter Hurley wrote:
>> 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
On Feb 02 Peter Hurley wrote:
> 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
> >
On Feb 02 Peter Hurley wrote:
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:
On 02/03/2015 03:44 AM, Stefan Richter wrote:
On Feb 02 Peter Hurley wrote:
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
On Feb 03 Peter Hurley wrote:
On 02/03/2015 03:44 AM, Stefan Richter wrote:
On Feb 02 Peter Hurley wrote:
[...]
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
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:
>
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:
On Jan 28 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:
>
On Jan 28 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:
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
Signed-off-by: Clemens
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
Signed-off-by: Clemens
14 matches
Mail list logo
