[Bug 601161] Re: sysfs reports invalid vendor id for firewire device

2011-01-14 Thread Clemens Ladisch
This behaviour still exists in the latest kernel. However, the IDs reported on the FireWire bus are not PCI IDs but FireWire IDs, which are 24-bit IEEE OUIs. 0xd00d1e is the correct vendor ID for Linux. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug

[Bug 601161] Re: sysfs reports invalid vendor id for firewire device

2011-01-10 Thread Seth Forshee
This report is against an early alpha kernel. Does the bug still exist in the latest kernel? ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because yo

[Bug 601161] Re: sysfs reports invalid vendor id for firewire device

2010-07-02 Thread Mathieu Trudel
This seems to be related to the addition of the "firewire" type of bus recently; the device would usually just be reported as a device on "pci" bus. -- sysfs reports invalid vendor id for firewire device https://bugs.launchpad.net/bugs/601161 You received this bug notification because you are a m

[Bug 601161] Re: sysfs reports invalid vendor id for firewire device

2010-07-02 Thread Mathieu Trudel
Confirmed; this device would usually show up as 0832:1180:0001:1179, Vendor "Ricoh Co Ltd", Product "R5C832 IEEE 1394 Controller". However, I am not certain it belongs to kernel, however I am not sure where else it would be. It certainly doesn't seem to have to do with udev, AFAICT. ** Changed in

[Bug 601161] Re: sysfs reports invalid vendor id for firewire device

2010-07-02 Thread Marc Tardif
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/51299547/AlsaDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/51299548/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/51299549/Card0.Amixer.valu