linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <20120418055139.GA25952@bitwizard.nl>
Date:	Wed, 18 Apr 2012 07:51:40 +0200
From:	Rogier Wolff <R.E.Wolff@...Wizard.nl>
To:	linux-kernel@...r.kernel.org
Subject: BCM36xx support. 

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.

(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).

Roger.

-- 
** R.E.Wolff@...Wizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
**    Delftechpark 26 2628 XH  Delft, The Netherlands. KVK: 27239233    **
*-- BitWizard writes Linux device drivers for any device you may have! --*
The plan was simple, like my brother-in-law Phil. But unlike
Phil, this plan just might work.
--
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/