lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <54D4B170.6070403@schorsch-tech.de>
Date:	Fri, 06 Feb 2015 13:20:00 +0100
From:	Georg Gast <georg@...orsch-tech.de>
To:	linux-kernel@...r.kernel.org
Subject: SJA1000: PCI based can bus card

Hi,
i have the following card:

[10b5:9050] (rev 01) Subsystem: PLX Technology, Inc. IXXAT CAN i165

lspci -x -d 10b5:9050
07:05.0 Network controller: PLX Technology, Inc. PCI <-> IOBus Bridge
(rev 01)
00: b5 10 50 90 03 00 80 02 01 00 80 02 10 00 00 00
10: 00 50 40 fe 01 a4 00 00 00 00 40 fe 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 b5 10 67 10
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 01 00 00

It offers an sja1000 can bus. It is a relatively old card. The 10b5:9050
suggested that the driver plx_pci + sja1000 are offering support for it,
but i guess it gets rejected by the subsystem id, but i cant figure out
if i have done it wrong.

from the output of the pci configuration space, i guess the subsystem id
is 1067 so i authored the appended patch. My added printk doesnt get
triggered, so i assume, the pci description is still wrong.

Any hints would be appreciated...

This is exactly the card.
http://www.bol-system.com/english/ixxat/ipci165pci.htm

Best regards
Georg Gast

View attachment "0001-IXXAT-CAN-i165.patch" of type "text/x-patch" (2133 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ