linux-kernel - [PATCH 0/2] janz: fix support for Janz CMOD-IO revision 1.0 hardware

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]

Date:	Tue, 11 Sep 2012 15:58:13 -0700
From:	"Ira W. Snyder" <iws@...o.caltech.edu>
To:	linux-kernel@...r.kernel.org
Cc:	linux-can@...r.kernel.org, sameo@...ux.intel.com,
	"Ira W. Snyder" <iws@...o.caltech.edu>
Subject: [PATCH 0/2] janz: fix support for Janz CMOD-IO revision 1.0 hardware

From: "Ira W. Snyder" <iws@...o.caltech.edu>

The Janz CMOD-IO Carrier Board hardware, revision 1.0 has several quirks
that do not effect newer revisions of the hardware. This series fixes both
quirks so that the old hardware works correctly.

The janz-cmodio MFD driver did not mask out the unused bits from the
modulbus_number sysfs file. On CMOD-IO revision 1.0, the upper bits have
random data. By masking out the bits, the correct number is presented to
userspace.

The janz-ican3 driver used the reset_assert and reset_deassert registers.
These registers do not exist on CMOD-IO revision 1.0. To work around the
problem, the hardware reset registers on the ican3 hardware itself are
used.

These are trivial fixes that fix support for some hardware which is currently
broken. It would be nice to get these into the current kernel release.

Ira W. Snyder (2):
  mfd/janz-cmodio: fix MODULBus number sysfs entry
  can: janz-ican3: fix support for older hardware revisions

 drivers/mfd/janz-cmodio.c    |    2 +-
 drivers/net/can/janz-ican3.c |    4 +---
 2 files changed, 2 insertions(+), 4 deletions(-)

-- 
1.7.8.6

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/