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-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY1PR11MB04398923A2A7D113C738523EECB80@BY1PR11MB0439.namprd11.prod.outlook.com>
Date:   Fri, 21 Dec 2018 01:02:23 +0000
From:   <Tristram.Ha@...rochip.com>
To:     <marex@...x.de>
CC:     <netdev@...r.kernel.org>, <Woojung.Huh@...rochip.com>,
        <andrew@...n.ch>, <f.fainelli@...il.com>
Subject: RE: [RFT][PATCH 4/7] net: dsa: microchip: Remove dev->txbuf

> On 12/20/2018 10:41 AM, Andrew Lunn wrote:
> > On Wed, Dec 19, 2018 at 05:20:33PM -0800, Florian Fainelli wrote:
> >> On 12/19/18 5:06 PM, Marek Vasut wrote:
> >>> Previous patches unconver that ksz_spi_write() is always ever called
> >>> with len = 1, 2 or 4. We can thus drop the if (len > SPI_TX_BUF_LEN)
> >>> check and we can also drop the allocation of the txbuf which is part
> >>> of the driver data. This wastes 256 bytes for no reason and can be
> >>> replaced with 8-byte stack allocated buffer, which is what this patch
> >>> does. This is an intermediate step though, which will go away after
> >>> regmap conversion.

The switch uses auto address increment and can return the whole register
space in 1 transfer.  Most switches have only 256 registers, so I just stopped
at that number for KSZ9477.

This read operation is mostly done by users to dump the registers for debugging.
The write operation can be used to setup registers from a file.

I mentioned before the driver can use the standard Linux register access API for
users to read the chip.  Maybe you also want to try that for debugging.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ