linux-kernel - Re: BCM36xx support.

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: <7383662.i0oNtC19fQ@flexo>
Date:	Thu, 31 May 2012 15:55:34 +0200
From:	Florian Fainelli <florian@...nwrt.org>
To:	Rogier Wolff <R.E.Wolff@...wizard.nl>
Cc:	linux-kernel@...r.kernel.org, linux-mips@...ux-mips.org
Subject: Re: BCM36xx support.

Hi Rogier,

First of all, you should have CC'd linux-mips, because that's where BCM63xx 
development happens.

On Wednesday 18 April 2012 07:51:40 Rogier Wolff wrote:
> 
> While working on SPI and I2C support for the BCM2835, I found the
> BCM63xx SPI driver in the kernel. Turns out that this support
> was partially merged: 
> 
> The support can only be enabled when BCM63xx configuration symbol
> is defined which menuconfig lists as: 
> 
>  Symbol: BCM63XX [=BCM63XX]                                                
>    Type  : unknown                                                           
> 
> I'd say the definition of this is not possible through the normal
> channels.
> 
> And in the driver (drivers/spi/spi-bcm63xx.c) I see: 
> 
> #include <bcm63xx_dev_spi.h>
> 
> but that file is not in the current git release.

No, it did not make it for a reason I ignore, probably miscommunication.

> 
> (some more googling has resulted in me finding out that I don't want
> to know how the 63xx SPI controller works as it's for a MIPS processor
> while the 2835 is ARM).

And so? if the core is the same, just use it on your platform too. If you have 
a look at the architecture files, you will see that the various BCM63xx SoC 
have their internal registers shuffled but the SPI core is always software 
compatible, another set of registers can be added for BCM2835.

I have no objection making such a driver more generic and not limited to 
bcm63xx like it is right now.
--
Florian
--
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/